Meta tags:
description= A high level overview of Datawrapper s API and how to get going.;
Headings (most frequently used words):
getting, started, basics, tutorials, locator, maps, references, integration, embedding, authentication, requesting, data, where, to, go, from, here, keep, your, token, secret, what, next,
Text of the page (most frequently used words):
you (34), api (19), and (18), your (18), the (16), token (14), datawrapper (11), for (9), that (8), with (8), access (8), from (7), can (7), create (7), need (7), about (6), chart (6), getting (6), #started (6), read (5), charts (5), visualization (5), where (4), data (4), http (4), request (4), get (4), this (4), guides (4), account (4), write (4), reference (4), here (3), documentation (3), rest (3), what (3), our (3), endpoints (3), build (3), email (3), response (3), have (3), information (3), user (3), any (3), new (3), not (3), give (3), want (3), select (3), folder (3), embed (3), are (3), adding (3), markers (3), creating (3), requesting (2), authentication (2), copy (2), page (2), intro (2), see (2), how (2), use (2), them (2), name (2), url (2), protected (2), https (2), your_token_here (2), all (2), find (2), note (2), scopes (2), keep (2), secure (2), app (2), after (2), will (2), scope (2), click (2), edit (2), more (2), script (2), call (2), browser (2), lets (2), let (2), integrations (2), team (2), visualizations (2), events (2), types (2), locator (2), map (2), next, updated, year, ago, continue, reading, straight, into, exist, ahead, something, amazing, would, love, hear, made, first, 62982, lisa, teams, products, chartcount, users, 1000, abridged, should, body, looks, similar, json, snippet, curl, header, authorization, bearer, now, string, replace, own, test, following, command, allows, make, sure, check, when, selecting, very, important, safe, doubts, someone, else, got, time, one, revoke, share, publicly, push, github, secret, location, like, password, manager, won, able, again, refresh, pressing, appear, generate, key, gets, stolen, without, knowing, thankful, didn, auth, still, change, later, only, choose, example, upload, required, different, requests, hit, button, open, option, which, provide, personal, every, head, tokens, designed, used, computer, security, reasons, case, proxy, around, possible, server, side, scripts, quick, cors, programatically, interface, update, many, things, come, viewer, editors, right, they, writing, their, articles, cms, other, could, invite, members, export, images, there, lot, possibilities, guidance, help, happy, know, think, anything, unclear, please, contact, directly, high, level, overview, going, powered, render, flags, google, amp, oembed, custom, code, responsive, iframe, embedding, others, presets, listening, interaction, using, webhooks, publish, integration, properties, references, line, arrow, area, point, maps, beginner, guide, connecting, external, sources, automatic, updates, live, moving, deleting, exporting, png, pdf, svg, publishing, choropleth, tutorials, statuses, errors, basics, jump, content, agents, visit, developer, llms, txt, index, pages, formatted, markdown, openapi,
Text of the page (random words):
getting started for ai agents visit https developer datawrapper de llms txt for an index of all pages formatted in markdown and endpoints in openapi jump to content guides api reference v3 0 guides v3 0 guides getting started getting started basics getting started intro to http and rest http statuses and errors response types tutorials creating a chart creating a choropleth map publishing a visualization exporting as png pdf svg deleting a visualization moving a visualization automatic updates for live data connecting visualizations to external data sources a beginner s guide with r locator maps creating a locator map adding point markers adding area markers adding line arrow markers references api reference visualization types visualization properties integration getting started with integrations using team webhooks for chart publish events listening to chart interaction events let others create datawrapper visualizations from presets embedding responsive iframe script embed custom embed code oembed google amp render flags powered by getting started a high level overview of datawrapper s api and how to get going click here to go directly to the api reference datawrapper api lets you programatically interface with your charts it lets you create and edit charts update your account information and many more things to come you can build a chart viewer and let editors embed charts right from where they are writing their articles your cms other integrations could invite new members to your datawrapper team or export charts as images there are a lot of possibilities and if you need any guidance or help this documentation is for you we are happy to know what you think of it or if anything is unclear please contact us at email protected a quick note about cors the datawrapper api is designed to be used in server side scripts or from a script on your computer for security reasons it is not possible to call the datawrapper api from the browser in case you need to do that you can build a proxy around the endpoints that you need to call from the browser authentication to use the datawrapper api you ll need to provide a personal access token with every request to create this token head to app datawrapper de account api tokens to create your token hit the create new access token button this will open the option to give your token a name and to select which read write access you want to give it for example if you want to get information about your account you ll need to select user read if you want to create charts and upload them in a folder you ll need to select chart read chart write and folder read folder write you can find required scopes for different api requests in our api reference only choose the scope you need not more if your api key gets stolen without you knowing it you ll be thankful that you didn t give it user or auth write access you can still change the scope later with a click on edit after pressing generate token your token will appear you won t be able to see the token again after you refresh the page so copy it to a secure location like to your password manager keep your token secret it is very important that you keep your token safe and secure do not share it publicly or push it to github if you have any doubts about if someone else got access to your api access token you can revoke it at any time in our app and create a new one requesting data now you have an api access token in all guides where you find the string your_token_here you have to replace that with your own token you can test it with the following command that allows you to access your account information note make sure to check user read when selecting scopes for your api token request curl request get url https api datawrapper de v3 me header authorization bearer your_token_here you should get a response body that looks similar to this json snippet abridged response id 62982 email email protected name lisa teams products chartcount 1 url v3 users 1000 that s it you made your first request with the datawrapper api go ahead and build something amazing we would love to hear about it where to go from here you can continue reading about http and rest or go straight into our api documentation and see what endpoints exist and how to use them updated about 1 year ago what s next intro to http and rest api documentation copy page authentication requesting data where to go from here
|
