{"__v":23,"_id":"54eb63b959b1172100334fb4","category":{"__v":8,"_id":"54eb63b959b1172100334faf","pages":["54eb63b959b1172100334fb4","54eb63b959b1172100334fb5","54eb63b959b1172100334fb6","551539c3c859ac2f0001b46b","55153c3ac28d6125001b886d","55153e1fc859ac2f0001b470","5515424bc28d6125001b887b","55154597f854a3190036872d","551547cdbc466623002afe73","56c06e1ccfc5470d0018915d"],"project":"54eb50e5615ffc1900305a16","version":"54eb63b859b1172100334fae","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-02-23T16:10:14.298Z","from_sync":false,"order":0,"slug":"getting-started","title":"Getting started"},"parentDoc":null,"project":"54eb50e5615ffc1900305a16","user":"54eb4fdedf7add210007b29b","version":{"__v":14,"_id":"54eb63b859b1172100334fae","forked_from":"54eb63a1867e1917009b711d","project":"54eb50e5615ffc1900305a16","createdAt":"2015-02-23T17:30:32.501Z","releaseDate":"2015-02-23T17:30:32.501Z","categories":["54eb63b959b1172100334faf","54eb63b959b1172100334fb0","54eb63b959b1172100334fb1","54eb63b959b1172100334fb2","54ed8dd4ab373e2300f50eae","54ed99b2ab373e2300f50ede","55153a6de68daa2f00cff838","551546edbc466623002afe72","5515472ac28d6125001b8884","55154749c28d6125001b8885","555d9b4106dfec0d00d38ea7","5613e06e433e5735007c7708","5624bbb785a31117001c5403","56669e857cc81e0d00253f8e","568b8d837a42220d00498311","56a632277ef6620d00e2f18a","56d8147c3eb4dd0b00201aac"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1"},"updates":[],"createdAt":"2015-02-23T16:10:14.980Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"**Welcome to Infobip API documentation!**\n\nThis document will provide instructions on how to quickly integrate Infobip messaging services into various solutions by using Infobip HTTP application programming interface (HTTP API). The HTTP API can be used for sending SMS messages, collecting delivery reports, making Number Lookup (number validation) requests and receiving inbound SMS messages sent from mobile phones.\n\nInfobip's API is based on REST standards, enabling you to use your browser for accessing URLs. In order to interact with our API, any HTTP client in any programming language can be used.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"If you don't have an Infobip account yet, please visit our [Sign-up](https://accounts.infobip.com/signup) page and create your free account.\",\n  \"title\": \"Note:\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Base URL\"\n}\n[/block]\nSubmit all requests to the base URL. All the requests are submitted thorough HTTP `POST`, `PUT` or `GET` method. Although you can use HTTP protocol, we strongly recommend you to submit all requests to Infobip SMS API over HTTPS so the traffic is encrypted and the privacy is ensured.\n\n**Base URL:** `https://api.infobip.com` \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Content-Type & Accept header\"\n}\n[/block]\nInfobip SMS API supports `JSON` and `XML` Content-Types and Accept criteria that should be specified in the header. If the Content-Type  is not specified you will receive a General error. Depending which Accept type is chosen in the deader for the request, the same one will be applied in the response.\n\n**Content-Type:**  `application/json` or  `application/xml`.\n\n**Accept header:**  `application/json` or  `application/xml`.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Authorization\"\n}\n[/block]\nWe support basic authorization using a username and password with Base64 encoding variation [RFC2045-MIME](https://www.ietf.org/rfc/rfc2045.txt).\n\nThe authorization header is constructed as follows:\n\n1. Username and password are combined into a string `username:password`.\n2. The resulting string is encoded using the [RFC2045-MIME](https://www.ietf.org/rfc/rfc2045.txt) variant of Base64.\n3. The authorization method and a space, like this: `\"Basic \"`, are put before the encoded string.\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Example:\",\n  \"body\": \"Username: `Aladdin`\\nPassword: `open sesame`\\n\\nBase64 encoded string: `QWxhZGRpbjpvcGVuIHNlc2FtZQ==`\\n\\nAuthorization header: `Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==`\"\n}\n[/block]\n\n------\n### **Next:** [Send your first SMS message](doc:send-sms).","excerpt":"This page will help you get started with Infobip API. You'll be up and running in a jiffy!","slug":"getting-started","type":"basic","title":"Introduction"}

Introduction

This page will help you get started with Infobip API. You'll be up and running in a jiffy!

**Welcome to Infobip API documentation!** This document will provide instructions on how to quickly integrate Infobip messaging services into various solutions by using Infobip HTTP application programming interface (HTTP API). The HTTP API can be used for sending SMS messages, collecting delivery reports, making Number Lookup (number validation) requests and receiving inbound SMS messages sent from mobile phones. Infobip's API is based on REST standards, enabling you to use your browser for accessing URLs. In order to interact with our API, any HTTP client in any programming language can be used. [block:callout] { "type": "info", "body": "If you don't have an Infobip account yet, please visit our [Sign-up](https://accounts.infobip.com/signup) page and create your free account.", "title": "Note:" } [/block] [block:api-header] { "type": "basic", "title": "Base URL" } [/block] Submit all requests to the base URL. All the requests are submitted thorough HTTP `POST`, `PUT` or `GET` method. Although you can use HTTP protocol, we strongly recommend you to submit all requests to Infobip SMS API over HTTPS so the traffic is encrypted and the privacy is ensured. **Base URL:** `https://api.infobip.com` [block:api-header] { "type": "basic", "title": "Content-Type & Accept header" } [/block] Infobip SMS API supports `JSON` and `XML` Content-Types and Accept criteria that should be specified in the header. If the Content-Type is not specified you will receive a General error. Depending which Accept type is chosen in the deader for the request, the same one will be applied in the response. **Content-Type:** `application/json` or `application/xml`. **Accept header:** `application/json` or `application/xml`. [block:api-header] { "type": "basic", "title": "Authorization" } [/block] We support basic authorization using a username and password with Base64 encoding variation [RFC2045-MIME](https://www.ietf.org/rfc/rfc2045.txt). The authorization header is constructed as follows: 1. Username and password are combined into a string `username:password`. 2. The resulting string is encoded using the [RFC2045-MIME](https://www.ietf.org/rfc/rfc2045.txt) variant of Base64. 3. The authorization method and a space, like this: `"Basic "`, are put before the encoded string. [block:callout] { "type": "success", "title": "Example:", "body": "Username: `Aladdin`\nPassword: `open sesame`\n\nBase64 encoded string: `QWxhZGRpbjpvcGVuIHNlc2FtZQ==`\n\nAuthorization header: `Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==`" } [/block] ------ ### **Next:** [Send your first SMS message](doc:send-sms).