igrantio-api-sandboxeslisted

# iGrant.io OID4VC API - Sandboxes ## When to use Use this skill when the task is one of these: - Make a test wallet that does not touch the data of the main wallet. - Create, read, update, delete, or list **sandbox organisations**. - Change the name, the logo image, or the cover image of a sandbox organisation. - Send **any** OID4VC request against a sandbox organisation, whatever the group of that request. The call style below applies to about 180 endpoints. A sandbox organisation is a **separate wallet inside your organisation**. It has its own credential definitions, presentation definitions, webhooks, and keys. You can test an issuance flow or a verification flow without a change to the main wallet. **Before you start**, the main wallet of the organisation must be deployed. See `igrantio-api-wallet-provider` for the deploy operation. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framewor