Get an API key

Four steps. Approvals daily.

Phase 1 keys go through a short waitlist. The application is a dossier like everything else here: it fills as you answer, and you see exactly what we receive.

Step 1 of 4 · Plan

Pick the plan to start on.

Everything is upgradable later without migration; limits move, the record does not.

FreeEnough to ship something real. No card. 1,000 credits / mo5 rps · 1 research slot ProA production catalog at shop scale. Usage, credits in plan50 rps · 5 research slots ScalePlatforms resolving other people's catalogs. Usage, credits in plan250 rps · 25 research slots

Every plan runs the same record and the same honesty rules; plans only move the limits. The math: 1 credit per resolve, search 2, research 25 / 100 / 400. Enterprise (contractual SLAs, EU pinning, private markets): talk to us.

Who is integrating.

Keys are issued to organizations; one organization, one ledger, one truthful name.

Work email

That address looks personal. Keys go to organizations; use your work email.

Name

A name is required; a person reads this application.

Organization

The organization is the account; agencies sign up per client.

Who gets keys: organizations and working developers; no sanctioned parties; no bulk re-publication; one organization, one ledger. Rules E-01 to E-06, stated in full in acceptable use. Refusals cite their rule; appeals are read by a person.

What you will resolve first.

Your key arrives with a working example for this category, so the first request is never a blank page.

Category or feed

Optional, but the welcome mail is better with it.

Expected volume

Pre-tuned to your plan; correct us if reality disagrees.

GTIN to product page in four requests. Test keys behave exactly like live ones against a frozen snapshot; the examples run as printed.

Review and sign.

This is the complete application; nothing else is collected.

PlanFree

Organization—

Work email—

First resolve—

I accept the Terms of service and have read the Privacy notice. Both are short on adjectives. We will process personal data through the API and need the DPA countersigned. Optional now; mandatory before personal data flows. Most catalog work never needs it. Send release notes. Monthly, plain text, that is all we send.

Keys are environment-scoped: gpd_test_ behaves exactly like gpd_live_. Prices change with 30 days notice; pinned API versions never change.

You're on the list.

Keys go out daily; yours arrives with a working example for your category.

1A person reviews the application against the rules it cites. Same day.
2The welcome mail carries your key and a resolved dossier for your category.
3GTIN to product page in four requests; the examples run as printed.

Wrong address? Reply to the confirmation mail and we correct it.