DoorDash Catalog Upload

This example shows how to request a temporary upload URL from EveryBite and then upload a DoorDash items.json catalog directly to private S3 storage.

DoorDash does not need an AWS account or AWS credentials for this upload. The temporary URL returned by EveryBite carries its own signature.

Request an upload URL

The EveryBite-issued DoorDash bearer token must be available in the EVERYBITE_DOORDASH_TOKEN environment variable.

curl --request POST \
  "https://api.everybite.com/graphql" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer ${EVERYBITE_DOORDASH_TOKEN}" \
  --data '{
    "query": "mutation { createDoorDashCatalogUpload { method uploadUrl objectKey expiresAt contentType } }"
  }'

Example response:

{
  "data": {
    "createDoorDashCatalogUpload": {
      "method": "PUT",
      "uploadUrl": "https://everybite-exchange-doordash.s3.us-east-1.amazonaws.com/...?X-Amz-Signature=...",
      "objectKey": "doordash/business_id=73878/date=2026-07-22/items.json",
      "expiresAt": "2026-07-22T15:30:00.000Z",
      "contentType": "application/json"
    }
  }
}

Upload items.json

Copy the complete uploadUrl from the response and use it before expiresAt:

curl --request PUT \
  --header "Content-Type: application/json" \
  --upload-file "/path/to/items.json" \
  "<paste-the-complete-uploadUrl-here>"

A successful S3 upload normally returns an empty response body. The uploaded object will be stored at the objectKey returned by the API, for example:

s3://everybite-exchange-doordash/doordash/business_id=73878/date=2026-07-22/items.json

Handling the upload URL

The temporary URL normally expires after approximately 15 minutes. Keep it quoted because it contains & characters, do not modify it, and send exactly Content-Type: application/json.

Overview

Core Concepts

SmartMenu API

GuestIQ

Atlas

Handling the upload URL

​Handling the upload URL

Handling the upload URL