Endpoints that upload audience data and metadata to Acoustic Exchange are considered to be a push-type audience producer. To initiate the data upload and related tasks, the endpoint calls APIs that are hosted by Acoustic Exchange.
For example, to avoid potential security concerns, business applications that are physically installed in a local computer network as an On Prem application typically connect to Acoustic Exchange as a push-type endpoint.
The following table identifies the APIs that the endpoint must call to support actions that are expected of a push-type audience producer.
| Action | API |
|---|---|
| Add a list to Acoustic Exchange that identifies segments that are ready for export to Acoustic Exchange. | POST /v1/endpoint/{endpointId}/segments |
| Replace a list on Acoustic Exchange that identifies segments that are ready for export to Acoustic Exchange. | PUT /v1/endpoint/{endpointId}/segments |
| Clear the list on Acoustic Exchange that identifies segments that are ready for export to Acoustic Exchange. | DELETE /v1/endpoint/{endpointId}/segments |
| Remove a specific segment from the list on Acoustic Exchange that identifies segments that are ready for export to Acoustic Exchange. | DELETE /v1/endpoint/{endpointId}/segments/{segmentId} |
| Upload audience data and metadata to Acoustic Exchange in CSV format. | POST /v1/jobs/{jobId}/data |
| Get a list of one or more jobs, identified by category, endpoint ID, or status. | GET /v1/jobs/{jobCategory} |
| Get a specific job, identified by job category and job ID. | GET /v1/jobs/{jobCategory}/{jobId} |
Comments
0 comments
Article is closed for comments.