Freesound API v2

REST discovered

Details Spec supplied by APIs.guru

URL: http://www.freesound.org/apiv2
Spec: https://api.apis.guru/v2/specs/freesound.org/2.0.0/swagger.json
Docs: https://freesound.org/docs/api/

Authentication

Freesound API credential (client ID, client secret/API key, redirect URL) ?token=<credential> + Freesound API credential (client ID, client secret/API key, redirect URL) Authorization: Token <credential> discovered

Freesound API credential (client ID, client secret/API key, redirect URL) compound Get key ↗

Create a Freesound account, then go to API credential request and request an API credential. The docs say the credential page shows a Client id plus a Client secret/Api key value; for simple token auth you use the Client secret/Api key, and for OAuth2 authorization-code flow you use the client_id and client_secret from the same credential. Configure the credential's redirect URL there if you will use OAuth2.

Freesound OAuth2 access token oauth2 discovered Set up OAuth ↗

Authorization: Bearer <credential>

First request a Freesound API credential at API credential request. Then implement the OAuth2 authorization-code flow described in Authentication: send users to https://freesound.org/apiv2/oauth2/authorize/ with client_id and response_type=code, then exchange the returned code at https://freesound.org/apiv2/oauth2/access_token/ using your client_id and client_secret to obtain an access token. Freesound states OAuth2 requests must be made over https.