Meta tags:
description=Learn how to implement an API for your service according to the IFTTT Service Protocol.;
keywords=ifttt applets connect connections integrate integration automate automation services recipes trigger action ifthisthenthat free;
author=IFTTT;

Headings (most frequently used words):

example, http, body, headers, response, authenticated, services, request, non, dynamic, tips, trigger, field, input, service, ingredients, api, fields, options, date, ifttt, parameters, authentication, refresh, user, action, queries, query, status, openapi, time, dropdowns, checkboxes, validation, based, url, examples, raw, on, authorization, token, limit, valid, invalid, paginated, page, general, requirements, tokens, information, triggers, identity, realtime, applet, templates, actions, definition, mobile, push, notification, short, message, long, post, plaintext, file, spreadsheet, phone, call, calendar, event, string, and, nested, what, is, how, to, use, it, next, steps, flow, contextual, location, pagination, https, prefix, endpoint, paths, codes, format, success, error, client, credentials, grant, redirect, denies, exchange, default, explicit, only, ok, unavailable,

Text of the page (most frequently used words):
the (297), ifttt (144), accept (126), #service (120), json (112), application (105), example (100), for (99), your (99), request (91), http (86), user (86), trigger (80), utf (79), api (78), charset (78), value (69), and (68), content (61), data (60), type (58), you (57), com (54), that (54), options (54), will (51), fields (49), url (48), response (47), body (47), headers (44), should (43), can (43), encoding (43), this (42), gzip (42), deflate (42), ingredient (41), endpoint (40), token (40), label (40), field (40), authorization (40), with (37), 200 (37), dynamic (37), post (34), use (32), status (32), object (32), string (30), have (30), bearer (30), which (29), not (28), action (26), following (25), random_uuid (24), authentication (24), services (23), row (23), each (23), https (22), query (22), authenticated (22), are (21), code (21), validation (21), provide (21), access (21), triggers (21), valid (20), trigger_identity (20), refresh (20), time (19), generate (19), used (19), host (19), applet (19), from (18), key (18), ingredients (18), limit (18), applets (17), set (17), drop (17), down (17), when (17), realtime (17), openapi (16), method (16), queries (16), b29a71b4c58c22af116578a6be6402d2 (16), information (16), input (16), new (16), personal (16), api_url_prefix (15), unique (15), based (15), get (14), may (14), main (13), configuration (13), make (13), values (13), users (13), page (13), optional (13), using (13), tokens (13), error (13), check (12), one (12), name (12), ifttt_service_key (12), street (12), art (12), array (12), non (12), user_access_token (12), list (12), actions (12), all (12), org (11), specific (11), contains (11), album_name (11), event (11), message (11), oauth2 (11), about (10), java (10), only (10), objects (10), sent (10), events (10), slug (10), how (9), implementation (9), server (9), file (9), 2013 (9), items (9), dynamically (9), banksy (9), ifttt_source (9), note (9), contextual (9), card (9), service_id (9), see (8), springframework (8), boot (8), src (8), definition (8), endpoints (8), fetch (8), select (8), timestamp (8), item (8), tips (8), board (8), has (8), validate (8), user_id (8), client (8), authorize (8), run (7), resources (7), version (7), spring (7), location (7), they (7), point (7), returned (7), option (7), was (7), images (7), cursor (7), every (7), other (7), requests (7), parameter (7), 400 (7), refresh_token (7), channels (7), best (6), next (6), create (6), web (6), return (6), generator (6), gradle (6), most (6), available (6), date (6), displayed (6), but (6), below (6), present (6), via (6), would (6), these (6), image_url (6), tags (6), posted_at (6), myrecipes (6), timezone (6), america (6), los_angeles (6), default (6), than (6), support (6), related (6), number (6), level (6), single (6), specified (6), same (6), trigger_slug (6), new_photo_in_album_with_hashtag (6), must (6), identifier (6), engine (6), light (6), after (6), client_id (6), flow (6), tools (5), calendar (5), import (5), add (5), able (5), true (5), javax (5), multiple (5), more (5), 04t09 (5), rows (5), 12345 (5), technology (5), 43245 (5), animals (5), cats (5), 32143 (5), dogs (5), 51231 (5), actual (5), facing (5), selector (5), sees (5), executed (5), categories (5), exchange (5), text (5), requires (5), before (5), contain (5), reference (5), responses (5), uniquely (5), future (5), two (5), created (5), urls (5), whether (5), given (5), once (5), settings (5), redirect_uri (5), what (4), twitter (4), top (4), map (4), public (4), class (4), static (4), build (4), into (4), false (4), swagger (4), there (4), requirements (4), some (4), does (4), list_album_photos (4), empty (4), 125 (4), result (4), 1d21c3cd2ed8441ea269dd554d2c8e54 (4), queryfields (4), pagination (4), private (4), checkbox (4), instead (4), manual (4), resource (4), sure (4), template (4), need (4), notification (4), keep (4), then (4), examples (4), triggerfields (4), description (4), area (4), exists (4), invalid (4), regardless (4), their (4), enabled (4), them (4), vehicle (4), identity (4), meta (4), invalid_grant (4), error_description (4), codes (4), access_token (4), grant_type (4), client_secret (4), represent (4), parameters (4), redirect (4), state (4), scope (4), errors (4), automation (3), automate (3), ios (3), google (3), docs (3), explore (3), connect (3), iftttapi (3), responseentity (3), annotation (3), find (3), generated (3), release (3), group (3), tech (3), generators (3), jackson (3), mkdir (3), 503 (3), require (3), nested (3), image (3), attribute (3), 9f99e73452cd40198cb6ce9c1cde83d6 (3), both (3), placed (3), categorized (3), category (3), itself (3), added (3), nyc (3), 04t03 (3), subsequent (3), 128 (3), brooklyn (3), triggered (3), identifying (3), pointing (3), describing (3), since (3), entity (3), slugs (3), action_slug (3), different (3), here (3), phone (3), call (3), mind (3), great (3), relevant (3), filename (3), because (3), document (3), plaintext (3), email (3), validated (3), however (3), please (3), trigger_field_slug (3), fresh (3), header (3), immediately (3), still (3), recent (3), notify (3), any (3), sending (3), delete (3), 7f7cd9e0d8154531bbf36da8fe24b449 (3), associated (3), longer (3), timeline (3), expire (3), 401 (3), www (3), form (3), urlencoded (3), step (3), secret (3), provided (3), protocol (3), wrong (3), success (3), prefix (3), contact (2), social (2), media (2), posts (2), apps (2), feeds (2), workflow (2), management (2), stories (2), discord (2), notion (2), spotify (2), plans (2), help (2), try (2), steps (2), app (2), gradlew (2), package (2), springapplication (2), springbootapplication (2), args (2), service_api_example (2), restcontroller (2), iftttapicontroller (2), override (2), our (2), own (2), implement (2), just (2), stubs (2), openapigenerate (2), yaml (2), plugin (2), annotations (2), servlet (2), wrapper (2), ones (2), describes (2), save (2), effort (2), implementing (2), unavailable (2), simple (2), represented (2), typically (2), query_slug (2), had (2), been (2), paginated (2), seijjh24ks (2), structure (2), post_photo_to_album (2), action_field_slug (2), checkboxes (2), deep (2), dropdowns (2), manually (2), grab (2), choices (2), 234325 (2), modified (2), during (2), actionfields (2), title (2), photo (2), push (2), start (2), contents (2), formatting (2), cells (2), spreadsheet (2), record (2), keeping (2), exist (2), saved (2), might (2), include (2), important (2), friendly (2), mobile (2), helpful (2), powerful (2), templates (2), 923 (2), market (2), san (2), francisco (2), 94103 (2), usa (2), enable (2), entering (2), exiting (2), sorry (2), potential (2), ideas (2), features (2), cards (2), validating (2), becomes (2), within (2), scenario (2), b959f481ef4f4a8ab0ec414f58991674 (2), display (2), 37ccb881af5542fe8c5534e9744b6116 (2), notifications (2), although (2), send (2), either (2), though (2), 100 (2), checks (2), poll (2), also (2), recommend (2), under (2), details (2), tab (2), seen (2), simply (2), correspond (2), through (2), 92429d82a41e93048 (2), notifies (2), calls (2), subscribe (2), called (2), stores (2), 14b9 (2), 1fd2 (2), acaa (2), 5df5 (2), 1383597267 (2), integer (2), unix (2), seconds (2), stream (2), order (2), descending (2), hashtag (2), required (2), its (2), indicate (2), heisenberg (2), owner (2), cannot (2), info (2), disclose (2), respond (2), shown (2), updated (2), 83465ab42 (2), c4f7defe91df9b23 (2), expiry (2), received (2), indicating (2), again (2), token_type (2), authorization_code (2), 67a8ad40341224c1 (2), example_channel (2), access_denied (2), a00caec8dbd08e50 (2), anti (2), forgery (2), authorizes (2), grant (2), response_type (2), over (2), expiring (2), format (2), something (2), went (2), raw (2), general (2), started (2), menu (2), privacy, partner, program, careers, developers, threads, pomodoro, productivity, webhooks, rss, latest, telegram, todoist, reminders, sms, botghost, assistant, sheets, instagram, integrations, developer, search, center, free, business, learn, testing, successful, curl, verbose, localhost, 8080, bootrun, autoconfigure, void, bind, implements, getstatus, now, download, plugins, dependency, snapshot, repositories, mavencentral, inputspec, projectdir, generatorname, configoptions, datelibrary, java8, interfaceonly, skipdefaultinterface, openapinullable, apipackage, modelpackage, model, sourcesets, srcdirs, dependencies, starter, annotationprocessor, processor, webmvc, final, fasterxml, core, openapitools, databind, nullable, compileonly, initialize, project, choice, tool, depend, stack, popular, codegen, formerly, standard, describe, none, vfrqpgzbmzjb8jpp3mbfqodt, 0715f98e65f749aba2fc243eac1e3c09, periodically, availability, thus, themselves, described, detail, results, 00z, 2014, timestamps, iso8601, formats, flavor, strings, above, table, sets, points, think, tabular, columns, query_field_slug, named, history, published, august, 2020, translates, connections, last, larger, attributes, control, endpont, max, populated, unlike, currently, database, identifies, execution, new_status_update, out, bansky, produces, end, occurred, endtime, starttime, least, included, quick, knows, good, starting, place, wrote, read, aloud, runs, like, separate, ingredient3, ingredient2, ingredient1, spreadsheets, folder, path, yet, track, savedat, tracks, appended, files, widely, subject, craft, delightful, html, accepted, enhance, long, truncated, character, restrictions, short, avoid, don, too, dense, inform, define, ask, various, guide, efficiently, defaults, lat, 783923707779095, lng, 122, 40864549999998, radius, address, zoom, specify, difficult, know, intends, known, across, boards, comes, handy, needs, depends, another, take, new_comment_on_card, allows, incredibly, useful, setting, favor, album, explanation, boolean, validity, possible, wlwfgkxfsxbafmt8yz7aloafdqo7mahy, 619fd42930f74b78abc4394ca7bfec5b, 23489759, 77956024, c5559d12d393b25c140364d891292e02233933a5, 1000, user_ids, trigger_identities, generally, receives, polled, even, likely, few, lot, extra, spent, processing, reducing, means, faster, improve, performance, integration, uuid, debug, arise, reconcile, logs, making, tell, checked, presence, utilizing, load, performing, less, frequently, leverage, relying, identities, alone, involving, oriented, near, instantly, write, hook, changes, rather, directly, polling, clean, remove, storage, lookup, stop, deletes, updates, such, wants, begins, cloud, associates, creates, many, consider, hypothetical, publish, connected, car, product, safely, ignored, relationship, between, assist, troubleshooting, thought, signature, recieve, first, minute, ffb27, a63e, 18e0, 18ad, 1383596355, pair, structured, follows, prevent, firing, explicit, provides, excludes, chronological, maximum, overridden, except, remain, indefinitely, roll, off, bottom, exceeds, ensure, experience, expect, hour, fire, expired, walter, white, dashboard, website, unchangeable, permanent, identify, advise, against, emails, usernames, numbers, changed, characters, full, username, identification, three, 434d757081c94013b1b28f2087d28a98, occasionally, verify, acquiring, considered, who, activated, c547cdfecf7e86cde678bc87de6fc87, d7676beda76c38762349bac98cba799, c8764378d9879ffeadfcc233effafb23bbdbfe, retrieved, retrieve, technically, permissible, refreshed, acceptable, previous, uses, continue, until, occurs, attempt, obtain, attempting, earlier, deny, denied, denies, original, along, channel, redirected, authenticate, prompt, 94b26e58a3a88d5c, 2fifttt, 2fchannels, 2fexample_channel, 2fauthorize, encourage, always, redirecting, specifying, way, repeat, begin, redirects, makes, configuring, credentials, source, account, supports, including, desired, interacts, designed, circumvent, requirement, approved, fetching, storing, basic, behalf, matching, passed, activity, element, property, whose, varies, bodies, moment, later, logic, 500, trying, reach, doesn, 404, isn, incoming, clarify, compression, post_photo, any_new_photo, scoped, current, appending, paths, designate, production, served, specifies, according, recommended, treat, follow, outlined, overview, faq, close, log,

Text of the page (random words):
s authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid body value string user input to be validated example post ifttt v1 triggers new_photo_in_album_with_hashtag fields album_name validate http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id b959f481ef4f4a8ab0ec414f58991674 value street art response your trigger field s dynamic validation endpoint should generate the following response http status 200 regardless of whether or not the user input is valid headers content type application json charset utf 8 for the body you get a json object which contains an object data body data valid boolean validity of user s input data message optional string explanation to display to user if input was invalid example valid input http 1 1 200 ok content type application json charset utf 8 data valid true example invalid input http 1 1 200 ok content type application json charset utf 8 data valid false message sorry no album exists with the name street art trigger field contextual validation contextual validation allows you to validate a trigger field based on the values of other trigger fields it is incredibly useful for validating multiple trigger fields in a single api call because contextual validation is a trigger setting validation will be available to every trigger field when contextual validation is enabled all trigger field dynamic validation endpoints for the trigger will not be used in favor of the single validate endpoint to enable this option for your trigger please contact support request ifttt will make the following request to your service api http method post url api_url_prefix ifttt v1 triggers trigger_slug validate headers authenticated services authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid body values object trigger fields with their values example post ifttt v1 triggers new_comment_on_card validate http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id b959f481ef4f4a8ab0ec414f58991674 values board new features card potential ideas example the use of contextual validation comes in handy when a trigger field needs to be validated but the validation depends on another trigger field take the following scenario the trigger has two trigger fields board and card the board name is unique and a card exists within a board however cards can have the same name across different boards validating that the card exists becomes simple because the value of board is known if dynamic validation is used for the card trigger field it is difficult to know which card the user intends to trigger on during validation if the user has multiple cards with the same name response your trigger s contextual validation endpoint should generate the following response http status 200 regardless of whether or not the user input is valid headers content type application json charset utf 8 for the body you get a json object which contains an object data body data object dynamic validation objects for each trigger field example valid input http 1 1 200 ok content type application json charset utf 8 data board valid true card valid true example invalid input http 1 1 200 ok content type application json charset utf 8 data board valid true card valid false message sorry no card exists with the name potential ideas in the new features board location based input location based trigger fields enable users to specify whether applets should run based on a point an area entering an area exiting an area or entering or exiting an area these fields can be dynamically validated below is an example of how location based fields are represented example triggerfields location lat 37 783923707779095 lng 122 40864549999998 radius 0 address 923 market st san francisco ca 94103 usa description 923 market st san francisco ca 94103 usa zoom 16 applet templates when you create a new trigger and define the data the trigger will make available via ingredients we ll ask you to provide examples of how the trigger would be best used in various categories of actions these examples should guide users to create powerful applets more efficiently from helpful defaults instead of empty fields below you ll find helpful tips for each of the action categories mobile push notification tips should be friendly and personal use you instead of my don t make the content too dense inform the user of the most important information about the event avoid ingredients that point to urls short message tips provide the most important information using ingredients that keep the message contextual to the event keep in mind that the message might be truncated based on character restrictions include a url ingredient if one is available long post tips use the post body field to craft a delightful message for users html is accepted so be sure to add formatting that might enhance the message keep in mind that this content is used in email actions which are widely used post title is the subject and post body is the body of the email plaintext file tips plaintext files are great for record keeping be sure to use all relevant ingredients in the plaintext body if the filename is static ex saved tracks on spotify one document will be created and then appended to for each subsequent event if the filename contains a dynamic ingredient ex track saved on savedat a new file will be created with each event because it will have a unique filename the folder path specified will be created if it does not yet exist for the user spreadsheet tips spreadsheets are great for record keeping be sure to use all relevant ingredients use to separate cells in a row of a spreadsheet ex ingredient1 ingredient2 ingredient3 if you would like to use an image in one of the cells use image ingredient 1 phone call tips the contents here will be read aloud when the phone call action runs keep that in mind when formatting the template a good starting place for this template is to reference the contents you wrote for the notification template calendar event tips you need to have at least one timestamp ingredient included in the quick add text so that the calendar action knows when to create the event if your trigger produces the start time and end time of the event be sure to use both ingredients in the template ex some event occurred from starttime to endtime actions each action requires a unique api endpoint request for each new trigger item ifttt will push data to your action endpoint with the following request structure http method post url api_url_prefix ifttt v1 actions action_slug headers authenticated services authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id random_uuid body actionfields object map of action field slugs to values user object information about the ifttt user related to this request ifttt_source optional object information about the personal applet on ifttt that triggered this request if present this will have an id uniquely identifying the applet and a url pointing to a web page describing it note that only the user will be able to see this page since personal applets are private in the future these fields may point to an entity other than a personal applet example post ifttt v1 actions new_status_update http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id 1d21c3cd2ed8441ea269dd554d2c8e54 actionfields title new banksy photo body check out a new bansky photo http example com images 125 ifttt_source id 2 url https ifttt com myrecipes personal 2 user timezone america los_angeles response your action endpoint should generate the response below http status 200 headers content type application json charset utf 8 a json object which contains an array data of a single item object body data 0 id string a database id timestamp url or other value which uniquely identifies the resource created or modified during action execution data 0 url optional string url to the created or modified resource example http 1 1 200 ok content type application json charset utf 8 data id 234325 url http example com posts 234325 action fields action fields can be populated via a static text input or a drop down unlike trigger fields action fields do not currently support dynamic validation with a drop down we provide two different choices a dynamic drop down selector we provide you with a unique api endpoint based on the action field s name you can use to dynamically grab the list of options from your server a manual drop down to manually add a list of options that the user can select from action field dynamic options dynamic dropdowns options have a label which the user sees and a value which is sent when the action is executed if you re using the dynamic drop down instead of the manual drop down options can be placed into categories one level deep users may select categorized options but may not select the category itself request for action fields using the dynamic drop down selector you can dynamically provide user specific options each time the action field is displayed ifttt will fetch a list of options from your action field s dynamic options endpoint http method post url api_url_prefix ifttt v1 actions action_slug fields action_field_slug options headers authenticated services authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid an empty json object body example post ifttt v1 actions post_photo_to_album fields album_name options http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate x request id 9f99e73452cd40198cb6ce9c1cde83d6 response your action field s dynamic options endpoints should generate the following response http status 200 headers content type application json charset utf 8 for the body you will get a json object which contains an array data of option objects body data label string a user facing label data value string the actual field value example http 1 1 200 ok content type application json charset utf 8 data label street art value 12345 label technology value 43245 label animals values label cats value 32143 label dogs value 51231 dynamic checkboxes options have a label which the user sees and a value which is sent when the action is executed request for checkbox action fields you can dynamically provide user specific options each time the checkbox list is displayed ifttt will fetch a list of options from your action field s dynamic options endpoint http method post url api_url_prefix ifttt v1 actions action_slug fields action_field_slug options headers authenticated services authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate x request id random_uuid an empty json object body example post ifttt v1 actions post_photo_to_album fields album_name options http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate x request id 9f99e73452cd40198cb6ce9c1cde83d6 response your action field s dynamic options endpoints should generate the following response http status 200 headers content type application json charset utf 8 for the body you will get a json object which contains an array data of option objects body data label string a user facing label data value string the actual field value example http 1 1 200 ok content type application json charset utf 8 data label street art value 12345 label technology value 43245 label animals values label cats value 32143 label dogs value 51231 queries each query requires a unique api endpoint request to fetch new query data ifttt will make the following request to your query endpoint with the following request structure http method post url api_url_prefix ifttt v1 queries query_slug headers authenticated services authorization bearer user_access_token accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id random_uuid headers non authenticated services ifttt service key ifttt_service_key accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id random_uuid body queryfields object map of query field slugs to values cursor optional string reference to the next page of the result set limit optional number max number of rows to return in a response default 50 user object information about the ifttt user related to this request ifttt_source optional object information about the personal applet on ifttt that triggered this request if present this will have an id uniquely identifying the applet and a url pointing to a web page describing it note that only the user will be able to see this page since personal applets are private in the future these fields may point to an entity other than a personal applet example post ifttt v1 queries list_album_photos http 1 1 host api example service com authorization bearer b29a71b4c58c22af116578a6be6402d2 accept application json accept charset utf 8 accept encoding gzip deflate content type application json x request id 1d21c3cd2ed8441ea269dd554d2c8e54 queryfields album_name street art ifttt_source id 2 url https ifttt com myrecipes personal 2 user timezone america los_angeles response your query endpont should generate the response below http status 200 headers content type application...