The Infogr.am REST API provides programmatic access to infographic creation, update, and download. The REST API identifies applications and users using OAuth-like protocol, responses are available in JSON format.
To acquire Infogr.am REST API credentials, please log in to infogr.am and open the following link.
Official Infogram API Libraries
- infogram-node - Node.js library
- infogram-php - PHP library
- infogram-java - Java library
- infogram-ruby - Ruby gem
Accessing Infogr.am REST API
To access Infogr.am REST API service you must have a valid Infogr.am API account. That account is associated with your Infogr.am user and every operation with REST API is performed on your user’s behalf.
API account contains two important pieces of information: the so-called “API key” and “API secret key”. API key is sent with every request to the REST API service and API secret key is used in API request signing.
Each request to the Infogr.am REST API service must be signed. Also, each request must have the
api_key parameter (in the query string or request body) which is equal to your account’s API key. Invalid or absence of both request signature and the
api_key parameter will lead to HTTP response with code 400 “Bad Request”.
REST API HTTP response
Each successful response comes with status code 200 “OK” or 201 “Created”. There is a possiblity that this may change in the future, however it will remain that a successful response can be identified with a status code number between 200 and 299.
Successful response body depending on the request type can contain data which can be either plain text or JSON structure if response header indicates appropriate content type (
Each non-successful response comes either with status code between 400 and 499 or between 500 and 599. Usually a more concrete description of the problem can be found in the response body.
Status codes between 400 and 499 indicate that there is something wrong with the request itself - it might be either incorrect (400 “Bad Request”), it might reference a non-existing resource (404 “Not Found”) or user on which behalf API is accessed to might have insufficient privileges to perform certain operation (403 “Forbidden”)
Status codes between 500 and 599 indicate some problem with the API service. Most probably you should retry the request after some time or, if nothing changes, contact Infogr.am support.