Approaches to integrating the API - do you map data types?

[aubergine]

I'm just starting out with the APIs and am trying to decide whether to map the data types generated by the service to a domain model, or just use them directly.

I wouldn't normally expose data contract types outside of the communication layer, but in this case the API is large and I don't have any experience of using it.

In your experience, is it worth building a separate domain model and mapping service types to and from this model when you call the API? Or do you just consume the service generated data types?

[AlgoTrader]

There is a new JSON API coming. Don't invest in SOAP too much, it will die.
JSON is easily mapped into objects in most of the languages. I think no need to transform replies into special objects in most cases

[aubergine]

Thanks.

I've seen some of the other threads about this - massively excited about the JSON version - I've signed up to the BDP but how do I actually get access to the new API? I can't find any info on it.

[AlgoTrader]

The new API is not ready yet, only early incomplete preview. You can write to bdp and get Application Key to use it.

Now is the time when SOAP development is useless (will have to rewrite later) and JSON development is too early. It will last for several months.