| URL Param |
Description |
| name |
The recipient's full name |
| email |
The recipient's email address |
| address1 |
The recipient's street address |
| address2 |
The recipient's extended address (e.g., apartment or suite) |
| State |
The recipient's state |
| zip |
The recipient's postal code |
| country |
The recipient's country |
Example usage: [https://app.sendoso.com/v2/plugin/sends?email=\{email\_address}](https://app.sendoso.com/v2/plugin/sends?email=\{email_address})
# Authentication & Authorization
Source: https://developer.sendoso.com/marketplace/overview/authentication
## Introduction
Sendoso follows the standard OAuth 2.0 spec, using the Authorization Code grant type.
OAuth is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords. This is known as a "two-legged" OAuth, or "two-step" authentication process. Refer to the [OAuth 2.0 Authorization Framework RFC: Section 4.1](https://www.rfc-editor.org/rfc/rfc6749#section-4.1) for additional details.
To authenticate with the Sendoso API using OAuth, you will need to first register your application and obtain a client ID and client secret. You can then use these credentials to request an access token from the Sendoso OAuth endpoint.
Once you have an access token, you can include it in the Authorization header of your API requests. For example, to make a GET request to the `GET /sends` endpoint, you would include the following header:
```js theme={null}
Authorization: Bearer YOUR_ACCESS_TOKEN
```
## Registering your application
To get started with the API, you’ll need a client ID and client secret. Request these credentials by contacting [developers@sendoso.com](mailto:developers@sendoso.com).
By default, the standard Postman redirect URI will be allowlisted. For production use, we recommend including your own redirect URI when reaching out to register your application.
## Authorization Flow
### 1. Direct user to authorization endpoint
The first step of the flow is to direct the user to the authorization endpoint providing as URL parameters its client identifier, requested scope, local state, and a redirection URI to which the authorization server will send the user-agent back once access is granted.
```js theme={null}
https://app.sendoso.com/oauth/authorize
```