Catalog Upload

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

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

Arguments

Argument	Type	Required	Description
`businessId`	`NonEmptyString!`	Yes	The business the catalog belongs to. Determines the S3 object key the upload URL points at.

businessId has no default. Omitting it is a GraphQL validation error and the request is rejected before it reaches the resolver. An empty string is rejected by the NonEmptyString scalar.

The value is used verbatim and is not validated for format. A malformed businessId produces a malformed object key rather than an error, so the upload lands in the wrong place without failing. Always check objectKey in the response to confirm what was written.

Request an upload URL

The EveryBite-issued bearer token must be available in the EVERYBITE_<provider-name>_TOKEN environment variable.

curl --request POST \
  "https://api.everybite.com/graphql" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer ${EVERYBITE_<provider-name>_TOKEN}" \
  --data '{
    "query": "mutation { create<provider-name>CatalogUpload(businessId: \"73878\") { method uploadUrl objectKey expiresAt contentType } }"
  }'

Example response:

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

The object key is derived from the businessId you supplied:

<provider-name>/business_id=<businessId>/date=<YYYY-MM-DD>/items.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-<provider-name>/<provider-name>/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

Arguments

Handling the upload URL

​Arguments

​Handling the upload URL

Arguments

Handling the upload URL