This endpoint provides a way to get details on the particular job, as long as you know the subscription_id and the job_id. Scheduled exports run at a regular cadence. Each individual run is considered a "job" and has a "job Id".
app_id | Unique identifier for Branch app of requested data.
Access-Token | Key that encapsulates the users permission w.r.t an org. Obtained from the Branch Dashboard needed for authentication.
organization_id | the organization Id with which the Access Token and subscriptions are associated
A persistent id for the specific subscription.
The relevant job Id.
Export Job success response
Export Job Body
A persistent identifier for this export job run
whether the job is in progress, succeeded or failed. Available options are PENDING_GENERATION, PENDING_UPLOAD, RUNNING, SUCCEEDED and FAILED
The earliest date for which exported objects will be included. Format is set to yyyy-MM-dd'T'HH:mm:ssZ. Timezone is UTC.
The latest date for which exported objects will be included. Format is set to yyyy-MM-dd'T'HH:mm:ssZ. Timezone is UTC. Please note that this includes data through the final millisecond. So if end_date is 2023-05-30T19:59:59, this export job run will include data through the final millisecond i.e. 2023-05-30T19:59:59.999.
if the export job is for a subscription with destination.subscription_type set to branch, then this will be an array of pre-signed S3 URLs for export files that you can then download.
Number of objects in the export (e.g. CSV rows).
Authentication Failed
"{\n \"error\": {\n \"message\": \"Authentication failed !\",\n \"code\": 400\n }\n}"
Job ID Not Found