How can we help you?

Popular searches
ExportWorkflowCatalog
HomeTechnical

The integration building blocks of the platform, what they do, and which one to choose for your needs.

Grand Shooting fits into your e-commerce chain: your PIM or ERP feeds the Catalog, the studios produce the media, and the approved media go back to your DAM, your website or your marketplaces. Everything you do in the interface (create a Production, upload media, approve, publish) can also be done programmatically.

Four building blocks

Building blockWhat it doesFor whom
REST APIRead and write the account data: References, Productions, media, Specifications, stock.Developers, integrators
OAuth applicationsConnect third-party software to a Grand Shooting account without sharing a token: the user authorizes the application.Software vendors, partners
WebhooksGet notified as soon as a media or a Reference is created, modified or deleted, without polling the API.Developers, integrators
MCP serverQuery Grand Shooting in natural language from an AI assistant (Claude…).Business users, support teams

Cookbooks walk you through the most common integrations, with curl and Python examples ready to copy.

Which building block?

  • Synchronize your Catalog from a PIM or an ERP: the API (POST /reference/bulk), called by your tool or by a scheduled job.
  • Retrieve the approved media for your DAM or your website: the API for the initial load, then the pictures/update webhooks to process only what changes.
  • Upload photos produced elsewhere (external studio, service provider): the upload API, by file or by URL.
  • Offer your software to every Grand Shooting customer: an OAuth application, which each account authorizes in a few clicks.
  • Answer one-off questions ("how many media are waiting for approval in Production X?"): the MCP server, without writing any code.

Concepts to know

The API uses the vocabulary of the platform (see the glossary), with a few different names:

In the interfaceIn the API
Reference (Catalog)reference
Media (photo, video, 3D, PDF)picture
Productionproduction, identified by bench_root_id
Production step (Live, Post-production, Exports / Approval)bench, with its benchsteptype
Specificationsspecification (format, category)
View codeview_type_code
Publicationbroadcast
Stock (Logistics)stock

Objects and their statuses are described in API concepts.

The complete API reference (every endpoint, its parameters and responses) is generated from the code: api.grand-shooting.com. Its OpenAPI specification can be downloaded from api.grand-shooting.com/swagger.json: give it to your coding agent so that it writes the integration with you.