Using the V2 API

URL Format

The following is the syntax for making Web API requests:

Example WEB API URL[module].[action].[format]
  • [module] - The API endpoint to call, e.g. blocks.
  • [action] - Each module supports multiple actions such as add, get, and delete.
  • [format] - This determines the response format. It can be either json for a JSON response or xml for an XML response.


HTTP Return codes

  • 2XX - The API call was successful.
  • 4XX - The API call had an error in the parameters. The error will be encoded in the body of the response.
  • 5XX - The API call was unsuccessful. You should retry later.

The formats supported are XML and JSON. Errors and success responses are described below while calls that provide information have their own return structure.


      <error>... error messages ...</error>
  "message": "error",
  "errors": [
    "...error messages..."


  "message": "success"


Each API call requires authentication. You must send the following HTTP parameters on your API calls. Your credentials will be the same as what you used for your SMTP authentication and/or website.

  • api_user - This is the same credential used for your SMTP settings, and for logging into the website.
  • api_key - This is the same password to authenticate over SMTP, and for logging into the website.

Example API URL with user & pass parameters

For detailed information on the available Web API methods, select one from the tree on the left.

Rate Limits

Twilio SendGrid has a default rate limit of 600 requests/minute on some of the V2 API endpoints. If you exceed that rate limit you will receive a 429 error response with a “too many requests” message.

Content-Type: application/json
X-RateLimit-Limit: 150
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1392815263

  "errors": [
      "field": null,
       "message": "too many requests"

This rate limit does not affect the V2 mail/send endpoint.

The Data

When you send data a GET request, it usually means that you're sending data in the URL's query string, the part after the '?' in the url, as a key/value pair. The key is defined by the place where you are sending the data and is assumed to be URL-safe, however the data you provide may not be. So, you should urlencode the value (or the data part) of any URL-passed information.

For example, when you query for "" you get the following URL:

Where "" was encoded to "" in the URL.

Most programming languages have support for urlencoding, but should you need a character lookup to reference, please see the Wikipedia doc about urlencoding.

See a mistake? Edit this page