View Push Campaign

View

get

View push campaign details.

Authorizations
AuthorizationstringRequired

API Key Authentication

Authentication is required in order to interact with Batch's APIs.

Batch implements authentication using API Keys, that we call the "REST API Key". You can find it on your dashboard.

Please make sure that you keep this key secret. You should never use it in client apps to call APIs from there as it would easily be extractable.

How to authenticate

In order to authenticate your requests, add your REST API Key in the Authorization header and prefix it by Bearer. Example: Authorization: Bearer bcd38d9rfb38ra28.

Query parameters
orchestration_idstringRequired

The id of the push campaign to fetch.

Example: orchestration_0664hyh918hr1gnzka9py5t62nrc0e1q
Header parameters
X-Batch-ProjectstringRequired

The unique project key, identifying a project on the Batch platform

Example: project_0664hxvwffvbpn278gxdyhsadddqgna6
Responses
chevron-right
200

Successful response with details about a push campaign.

application/json

Detailed configuration for a push campaign orchestration.

idstringOptional

Unique identifier for the push campaign.

Example: orchestration_0664hyh918hr1gnzka9py5t62nrc0e1q
typestring · enumOptional

Type of orchestration.

Example: campaignPossible values:
namestringOptional

Name of the orchestration.

Example: Soldes d'été
statusstring · enumOptional

Current status of the orchestration.

Example: runningPossible values:
sourcestring · enumOptional

Source of the orchestration creation.

Example: dashboardPossible values:
labelsstring[]Optional

Labels associated with the orchestration.

Example: ["LABEL1","LABEL2"]
created_datestring · date-timeOptional

Date and time when the push campaign was created.

Example: 2026-03-18T09:15:00Z
updated_datestring · date-timeOptional

Date and time when the push campaign was last updated.

Example: 2026-04-12T16:40:00Z
start_timestring · date-timeOptional

Date and time when the orchestration starts.

Example: 2026-04-20T14:00:00Z
get
/orchestrations/view

Request structure

Route

The orchestration API exposes a GET endpoint that allows you to export message details for a specific Push Campaign. This includes information such as targeting query, push content, mobile landing keys.

/orchestrations/view

Headers and authentication

See Overview → Using Project APIs.

Query parameters

See the API Description.

Responses

Success

A successful GET request to this endpoint will return an HTTP 200 OK response. The body of the response will contain a JSON object with the details for the requested orchestration.

Response Body

The main JSON object contains the following fields:

  • id (string): The unique identifier of the push campaign for which details are being returned.

  • messages (array): An array of objects, where each object contains the push content. This can include:

    • Variant Detail for A/B tested orchestrations.

    • Multi-language Detail.

Failure

If the GET data does not meet the API requirements you will receive an actionable error message. Contact us at [email protected]envelope if you need further support.

See the list of potential failures in the API Description.

Last updated