{"_id":"543772b63474fb0800a20f25","__v":4,"is_link":false,"type":"basic","updates":[],"project":"543772b63474fb0800a20f1f","user":"5437725a4e799808006da486","api":{"url":"","auth":"never","basic_auth":false,"params":[],"results":{"codes":[]},"try":true,"settings":""},"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Overview\"\n}\n[/block]\nThe Worldbox  application-programming interface (API) is a set of programming instructions  and standards for accessing our worldwide company index and place orders and retrieve company reports, credit reports, financial data and legal documents.\n\nThe API is intended to return the requested company document in all available formats - including XML. The returned files are \"embedded\" as base64 encoded string the JSON response. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Get a test account\"\n}\n[/block]\nPlease contact our account manager for the access to the test environment. Don’t hestiate to email us directly at info:::at:::worldbox.com or call us at +41 44 391 34 31.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"REST Architecture\"\n}\n[/block]\nThe Worldbox webservice API is completely designed in within the REST architecture. REST is not a technology  it’s rather an architectural style of exposing API to the web service consumers. An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., a URI in HTTP). \n\nFor more information please go ahead to our dedicated page [REST Webservice](doc:rest-webservice).\n[block:api-header]\n{\n  \"title\": \"API Host\"\n}\n[/block]\nhttp://testapi.worldbox.ch (Development)\nhttps://api.worldbox.ch (Production)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Authentication\"\n}\n[/block]\nWorldbox uses  sessionless authentication.  For each request an API Key and API Secret has to be included into the request-header. Think of username/password for authentication, but it’s not per person, it’s per API consumer.\n\nMost client software provides a simple mechanism for supplying a user name and password and will build the required authentication headers automatically. For example you can specify the -u argument with curl as follows\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"curl -D- -u fred:fred -X GET -H \\\"Content-Type: application/json\\\" https://api.worldbox.ch/v1/companies/?q=worldbox&countrycode=CH \",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Supplying Basic Auth headers\"\n}\n[/block]\n If you need to you may construct and send basic auth headers yourself. To do this you need to perform the following steps:\n\n   1.  Build a string of the form apikey:apisecret\n   2.  Base64 encode the string\n   3. Supply an \"Authorization\" header with content \"Basic \" followed by the encoded string,\n       e.g. \"Basic YWRtaW46YWRtaW4=\"\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"curl -D- -X GET -H \\\"Authorization: Basic ZnJlZDpmcmVk\\\" -H \\\"Content-Type: application/json\\\" https://api.worldbox.ch/v1/companies/?q=worldbox&countrycode=CH\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Convention\"\n}\n[/block]\n   * Client - Client application.\n   * Status - HTTP status code of response.\n   * All the possible responses are listed under ‘Responses’ for each method. Only one of them is issued per request server.\n   *  All response are in JSON format.\n   * All request parameters are mandatory unless explicitly marked as [optional]","githubsync":"","hidden":false,"link_url":"","title":"Getting Started with Worldbox API","version":"543772b63474fb0800a20f22","category":"543772b63474fb0800a20f23","createdAt":"2014-10-10T05:46:30.537Z","excerpt":"This page will help you get started with Worldbox API. You'll be up and running in a jiffy!","order":0,"slug":"getting-started","link_external":false,"sync_unique":"","parentDoc":null,"isReference":false,"next":{"description":"","pages":[]},"childrenPages":[]}

Getting Started with Worldbox API

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

[block:api-header] { "type": "basic", "title": "Overview" } [/block] The Worldbox application-programming interface (API) is a set of programming instructions and standards for accessing our worldwide company index and place orders and retrieve company reports, credit reports, financial data and legal documents. The API is intended to return the requested company document in all available formats - including XML. The returned files are "embedded" as base64 encoded string the JSON response. [block:api-header] { "type": "basic", "title": "Get a test account" } [/block] Please contact our account manager for the access to the test environment. Don’t hestiate to email us directly at info@worldbox.com or call us at +41 44 391 34 31. [block:api-header] { "type": "basic", "title": "REST Architecture" } [/block] The Worldbox webservice API is completely designed in within the REST architecture. REST is not a technology it’s rather an architectural style of exposing API to the web service consumers. An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., a URI in HTTP). For more information please go ahead to our dedicated page [REST Webservice](doc:rest-webservice). [block:api-header] { "title": "API Host" } [/block] http://testapi.worldbox.ch (Development) https://api.worldbox.ch (Production) [block:api-header] { "type": "basic", "title": "Authentication" } [/block] Worldbox uses sessionless authentication. For each request an API Key and API Secret has to be included into the request-header. Think of username/password for authentication, but it’s not per person, it’s per API consumer. Most client software provides a simple mechanism for supplying a user name and password and will build the required authentication headers automatically. For example you can specify the -u argument with curl as follows [block:code] { "codes": [ { "code": "curl -D- -u fred:fred -X GET -H \"Content-Type: application/json\" https://api.worldbox.ch/v1/companies/?q=worldbox&countrycode=CH ", "language": "shell" } ] } [/block] [block:api-header] { "type": "basic", "title": "Supplying Basic Auth headers" } [/block] If you need to you may construct and send basic auth headers yourself. To do this you need to perform the following steps: 1. Build a string of the form apikey:apisecret 2. Base64 encode the string 3. Supply an "Authorization" header with content "Basic " followed by the encoded string, e.g. "Basic YWRtaW46YWRtaW4=" [block:code] { "codes": [ { "code": "curl -D- -X GET -H \"Authorization: Basic ZnJlZDpmcmVk\" -H \"Content-Type: application/json\" https://api.worldbox.ch/v1/companies/?q=worldbox&countrycode=CH", "language": "shell" } ] } [/block] [block:api-header] { "type": "basic", "title": "Convention" } [/block] * Client - Client application. * Status - HTTP status code of response. * All the possible responses are listed under ‘Responses’ for each method. Only one of them is issued per request server. * All response are in JSON format. * All request parameters are mandatory unless explicitly marked as [optional]