Retrieve india gst config
This store’s India GST supplier registration: the GSTIN, the registered legal name and address, the default rate for unclassified goods, and the invoice-number prefix. A STORE THAT HAS NOT CONFIGURED GST IS A 404, which is a state to branch on rather than an error. There is no empty document to read: a configuration with no GSTIN is not a registration, and one would fail validation if you sent it back. EVERY FIELD HERE IS STAMPED ONTO INVOICES ISSUED AFTER IT. A wrong GSTIN or legal name does not error, it prints wrong legal documents, and the failure surfaces months later at filing. state_code is DERIVED from the GSTIN’s own first two digits. It decides the tax split on every invoice, so it cannot be set independently: see the PUT. updated_at is ALSO THE VERSION TOKEN. Send it back as expected_updated_at on the PUT and your write refuses rather than reverting a change you never saw.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Response
Success
