API overview & authentication (Deep Art API)

Category: Deep Art API
Section: Getting started & authentication

Contents

• What the API does (at a glance)
• Credentials you’ll use
• Get your credentials (Developer Dashboard)
• Choose a usage plan
• Make a first test call (high‑level)
• Keep your keys safe
• Where to get help & track changes
• See also

What the API does (at a glance)

The Deep Art API lets you send an image with a chosen style, then fetch the processed result programmatically. A typical flow is: discover styles → submit an image with a style → poll for result → download.

Credentials you’ll use

From the Developer Dashboard you can work with:

• API Key — a single key value used by some endpoints.
• Access Key + Secret Key — a key pair you can generate/rotate via the dashboard.
• Action: Generate New Access Keys (creates a new pair; old keys should be rotated/revoked if no longer needed).

If keys shown in a browser tab or screenshot could be exposed, rotate them immediately.

Get your credentials (Developer Dashboard)

1. Sign in to the Developer Dashboard.
2. In API Credentials, copy your API Key or generate a new Access/Secret pair.
3. Store the values in a secure location (see Keep your keys safe below).

Choose a usage plan

On the dashboard you’ll find API Usage Plans (including a free Test Plan trial) and paid tiers with daily request quotas. Pick the plan that fits your volume; you can contact the team for an Unlimited option.

Make a first test call (high‑level)

Follow the sequence below (endpoint details are covered in the endpoint guides):

1. List styles to pick a style identifier.
2. Upload an image with the chosen style.
3. Check status until the job finishes, then download the result.

Keep your keys safe

• Never commit keys to public repos or ship them in client apps.
• Prefer environment variables or a secret manager on servers/CI.
• Rotate keys regularly and revoke ones you no longer use.
• Share per‑project keys on a need‑to‑know basis only.

Where to get help & track changes

• Docs — the top navigation in the Developer site includes Docs for request/response details.
• Support — use the Support link in the developer navigation to reach the team.
• Release information — watch the developer site for updates to endpoints, quotas, and SDKs.

See also

• API usage plans — pricing & daily quotas
• Manage API keys — create, rotate, revoke
• Quick start (cURL): list styles → upload → fetch result
• Errors & rate limits — troubleshooting