Extracts

1 operation in the Adverity Connect API. Replace {{INSTANCE}} and {{KEY}} in the examples with your instance and API key. How authentication works.

Requeue extracts for re-import to destinations

POST/api/v1/extracts/requeue/

API key permissionDestination: Writedestination:write

Triggers a requeue of the specified extracts, re-importing them to their destination tables. By default extracts are processed sequentially (in chronological order), which is appropriate for historical data loads. Set sequential=false for parallel processing.

Request bodyrequired

application/json

Body schema

object RequeueExtractsRequestSchema

• extract_idsarray of integerrequired
• binding_idsarray of integernullable
  Attributes

  • array of integer

  • null

• sequentialboolean

  Default true

Responses

200OKapplication/json

Response schema

object RequeueExtractsResponseSchema

• messagestringrequired
• extract_idsarray of integerrequired
• extract_countintegerrequired

RequestcURL

curl --request POST 'https://{{INSTANCE}}/api/v1/extracts/requeue/' \
  --header 'Authorization: Bearer {{KEY}}' \
  --header 'Content-Type: application/json' \
  --data '{
    "extract_ids": [
      1
    ],
    "binding_ids": [
      1
    ],
    "sequential": true
  }'

Response200

{
  "message": "string",
  "extract_ids": [
    1
  ],
  "extract_count": 1
}

Was this page helpful? Yes No