[This topic is pre-release documentation and is subject to change.]
Either creates a new Profile type or updates the type if it already exists.
The request is constructed as follows:
|HTTP Verb||Request URI|
|Hub-endpoint||Yes||The base URL for your Customer Insights Hub|
|profileTypeName||Yes||The name of the Profile definition to retrieve|
|locale-code||No||The localization code to apply to any returned properties. If no locale code is specified, then 'en-us' is used as default.|
A JSON object describing a Profile type.
The response includes an HTTP status code and a set of response headers.
- 200 (OK) - if the request completed successfully.
- 201 (Created) - if the request was accepted.
- 202 (Accepted) - if the request was accepted.
Type provisioning is typically a long running operation. The initial request will come back with HTTP Accepted (202) and a location header with a URL of the form:
The status of the operation can be queried on the URL above. It will return status 202 until the operation finishes, at which time it will send back a 201 or 200.