Helping Businesses Get Found: The Partner Training Course

What it does: It provides official U.S. forecasts, observations, alerts, stations, and grid data. Coverage is primarily the United States and its territories.

How it works: Your server requests a location or endpoint and receives GeoJSON or JSON-LD. Forecasts usually require a point lookup followed by the returned grid endpoint.

How we'd add it to a customer's site:

1. Add an identifying User-Agent
2. Look up the customer's coordinates
3. Call the points and forecast endpoints
4. Cache and display the result

Example: A roofing company can show today's forecast and active storm warnings.

Know this: There is no fee or API key, but reasonable unpublished rate limits apply.

🔗 Website · Developer docs

What it does: It supplies worldwide current weather, forecasts, air pollution, geocoding, and map layers. Paid products add longer forecasts, history, and specialized data.

How it works: Your server sends coordinates and an API key to a REST endpoint. The service returns JSON, XML, or map tiles depending on the product.

How we'd add it to a customer's site:

1. Create an account and key
2. Geocode the business location
3. Call the required weather endpoint
4. Cache and display selected fields

Example: A landscaping company can show current conditions and a five-day forecast.

Know this: The free plan has product and call limits, while advanced forecasts and historical data cost extra.

🔗 Website · Developer docs

What it does: It provides global current conditions, forecasts, weather maps, astronomy, air quality, and location search. Higher plans add longer history, forecasts, marine data, and specialist fields.

How it works: The website's server calls an HTTPS endpoint with a key and location query. The response arrives as JSON or XML for rendering.

How we'd add it to a customer's site:

1. Register for an API key
2. Choose a forecast or current endpoint
3. Call it from the server
4. Cache and format the response

Example: A tour operator can show a three-day destination forecast.

Know this: The free commercial plan is limited to 100,000 calls monthly and a shorter forecast and history window.

🔗 Website · Developer docs

What it does: It provides real-time, forecast, historical, map, and weather-event data worldwide. Premium layers cover subjects such as air quality, pollen, lightning, and routes.

How it works: Your backend sends coordinates, requested fields, and a key to its REST API. It receives structured JSON timelines or map data.

How we'd add it to a customer's site:

1. Create a developer account
2. Copy the private API key
3. Request fields for a location
4. Cache and display the forecast

Example: An outdoor-event company can warn customers about rain or strong wind.

Know this: The free plan has shorter forecasts, fewer premium layers, and tighter usage limits.

🔗 Website · Developer docs

What it does: It exposes EPA environmental records, including Safe Drinking Water Information System data. Developers can query facilities, violations, enforcement, contaminants, and other program tables.

How it works: A request names an Envirofacts table, filters, and output format in the URL. The service returns JSON by default, with formats such as CSV and XML also available.

How we'd add it to a customer's site:

1. Identify the SDWIS table and fields
2. Build a filtered server request
3. Page large result sets
4. Explain the results clearly

Example: A water-treatment company can show public-system violations for a service area.

Know this: The data model is complex, and requests must complete within EPA's processing limit.

🔗 Website · Developer docs

What it does: They provide streamflow, gauge height, groundwater, daily values, monitoring sites, and water-quality records. The modern APIs support REST and OGC-compatible access.

How it works: Your server queries monitoring locations, time ranges, and measured parameters. The API returns machine-readable observations and metadata.

How we'd add it to a customer's site:

1. Find nearby monitoring locations
2. Choose continuous or daily values
3. Request only the needed period
4. Cache and chart the readings

Example: A kayak outfitter can publish the latest river level near its launch.

Know this: Legacy WaterServices are scheduled for retirement, so new work should use the modern endpoints.

🔗 Website · Developer docs

What it does: It combines discrete water-quality observations from hundreds of federal, state, tribal, and local organizations. Users can search sites, activities, results, and biological records.

How it works: A server submits geographic, date, organization, or characteristic filters to a web service. Results are returned in supported machine-readable download formats.

How we'd add it to a customer's site:

1. Choose a location and characteristic
2. Call the appropriate service
3. Limit and cache the results
4. Summarize units and sample dates

Example: A lake-management company can show recent bacteria or nutrient samples.

Know this: Large or broad searches can be slow, and measurements from different organizations may not be directly comparable.

🔗 Website · Developer docs

What it does: It provides current and forecast U.S. air-quality information, observations, and reporting-area data. Its outputs include AQI values and pollutant measurements.

How it works: Your backend calls an endpoint with an API key, location, and requested format. The service returns observations or forecasts as JSON, CSV, or files.

How we'd add it to a customer's site:

1. Register for an API key
2. Select a ZIP code or coordinates
3. Request current AQI or forecasts
4. Cache and show health labels

Example: A gym can show whether outdoor classes are advisable today.

Know this: Registration and attribution are required, and preliminary observations can later be revised.

🔗 Website · Developer docs

What it does: GIBS serves NASA Earth-observation imagery as ready-to-use global map layers. It covers fires, clouds, storms, sea ice, vegetation, and many other measurements.

How it works: A map requests dated image tiles through WMTS, WMS, or tiled endpoints. GIBS renders scientific datasets into images that the browser can place on a map.

How we'd add it to a customer's site:

1. Choose a GIBS layer
2. Add a compatible map library
3. Configure the tile endpoint and date
4. Add legends and attribution

Example: A coastal tour company can display recent satellite imagery around its harbor.

Know this: Many layers are scientific visualizations rather than street-level or real-time aerial photographs.

🔗 Website · Developer docs

What it does: They search, process, analyze, and deliver Sentinel and other Earth-observation imagery. Available services include catalog, processing, statistics, batch, and OGC APIs.

How it works: A backend obtains an OAuth token and submits an area, time range, collection, and processing script. The service returns images, raw bands, metadata, or statistics.

How we'd add it to a customer's site:

1. Create a Data Space account
2. Register an OAuth client
3. Search imagery for the area
4. Process and display the result

Example: A farm consultant can show recent vegetation-health imagery for a field.

Know this: Free general-user quotas limit requests and processing units, and cloud cover must be handled.

🔗 Website · Developer docs

What it does: They let customers search, order, process, analyze, and stream Planet's satellite imagery. Products include frequent medium-resolution coverage and high-resolution tasking.

How it works: An authenticated server searches the imagery catalog by area and date. It then activates, orders, processes, or streams licensed assets through other endpoints.

How we'd add it to a customer's site:

1. Purchase suitable imagery access
2. Create API credentials
3. Search an area and date range
4. Order and securely serve assets

Example: A construction firm can compare recurring images of a large project site.

Know this: Imagery availability, licensing, resolution, and price depend on the purchased product and contract.

🔗 Website · Developer docs

What it does: It provides interactive maps, geocoding, routes, address validation, street imagery, and place information. Web and mobile SDKs support polished location experiences.

How it works: The browser loads a Google SDK while sensitive web-service calls can run through the backend. API keys identify the project, and each billable event is metered by SKU.

How we'd add it to a customer's site:

1. Create a billing-enabled Cloud project
2. Enable only required APIs
3. Restrict the API key
4. Add the map or service call

Example: A plumber can show its service area and route customers to the shop.

Know this: Billing must be enabled, and usage beyond each SKU's monthly free cap is charged.

🔗 Website · Developer docs

What it does: It provides customizable maps, geocoding, search, navigation, directions, and geographic data tools. Designers can create branded map styles and data layers.

How it works: A web SDK fetches styled vector tiles with a public token, while server APIs handle searches and routes. Map loads and requests are counted against product-specific quotas.

How we'd add it to a customer's site:

1. Create an account and token
2. Design or select a map style
3. Add the web map SDK
4. Restrict tokens and monitor usage

Example: A real-estate agent can display listings on a branded neighborhood map.

Know this: Free allowances vary by product, and Mapbox attribution and token-security rules apply.

🔗 Website · Developer docs

What it does: HERE offers maps, geocoding, routing, traffic, places, weather, and fleet-oriented location services. It is especially strong in automotive and logistics applications.

How it works: Your application sends authenticated REST requests or uses a HERE SDK. The service returns JSON, map tiles, routes, traffic, or other location data.

How we'd add it to a customer's site:

1. Create a HERE project
2. Generate credentials
3. Choose map or REST services
4. Cache permitted results and display them

Example: A delivery company can calculate routes and estimated arrival times.

Know this: The limited base allowance and licensing rules differ across services and use cases.

🔗 Website · Developer docs

What it does: They provide maps, search, routing, traffic, geofencing, and location services. The platform supports web, mobile, automotive, and logistics projects.

How it works: The application calls REST endpoints or loads an SDK with an API key. Responses contain JSON route or search data, while map services return tiles.

How we'd add it to a customer's site:

1. Open a developer account
2. Create an API key
3. Select the required SDK or endpoint
4. Add caching and usage controls

Example: A towing company can display traffic-aware travel times.

Know this: Free quotas are limited, and higher volume or advanced products require paid access.

🔗 Website · Developer docs

What it does: It offers maps, geocoding, routing, places, isolines, and spatial-analysis APIs. It uses OpenStreetMap and other open geographic sources.

How it works: Your server or browser sends an API-key-authenticated request with an address or coordinates. It receives JSON, GeoJSON, or map tiles.

How we'd add it to a customer's site:

1. Create a Geoapify project
2. Generate and restrict a key
3. Call the needed endpoint
4. Cache results and add attribution

Example: A restaurant can show nearby parking, hotels, and transit stops.

Know this: Monthly credits and rate limits apply, and open-data attribution must remain visible.

🔗 Website · Developer docs

What it does: It exposes population, housing, business, economic, and demographic datasets from the Census Bureau. Queries can target states, counties, tracts, places, and other geographies.

How it works: A URL specifies the dataset, variables, year, and geography. The API returns a compact JSON array containing column names and rows.

How we'd add it to a customer's site:

1. Choose a dataset and year
2. Find the required variables
3. Request the customer's geography
4. Transform and label the response

Example: A retailer can show local population and household statistics in a market report.

Know this: A key is required above the unauthenticated daily threshold, and variable codes need careful interpretation.

🔗 Website · Developer docs

What it does: It searches metadata for datasets published by U.S. government organizations. Results describe datasets and link to their actual files or agency APIs.

How it works: A client calls CKAN action endpoints with search terms, organizations, or tags. The response is JSON metadata rather than the underlying dataset itself.

How we'd add it to a customer's site:

1. Define a focused catalog search
2. Call package_search from the backend
3. Extract current resource links
4. Display sources and update dates

Example: A grant consultant can build a directory of relevant federal datasets.

Know this: The API catalogs metadata only, so each linked dataset may require a different download or API process.

🔗 Website · Developer docs

What it does: It provides economic time series, releases, categories, sources, maps, and historical revisions. Data includes rates, employment, prices, housing, and regional indicators.

How it works: Your server calls a REST URL with a free API key and series parameters. It receives JSON or XML observations and metadata.

How we'd add it to a customer's site:

1. Create a free FRED account
2. Request an API key
3. Select series IDs
4. Cache and chart observations

Example: A mortgage broker can display current and historical interest-rate trends.

Know this: The limit is 120 requests per minute, and some third-party series have separate copyright restrictions.

🔗 Website · Developer docs

What it does: It provides programmatic access to thousands of government datasets hosted on Socrata portals. Common subjects include permits, inspections, crime, finance, and service requests.

How it works: Each dataset has a resource identifier and a REST endpoint on its government portal. SoQL parameters filter, group, sort, and aggregate returned JSON rows.

How we'd add it to a customer's site:

1. Find the official dataset
2. Copy its resource identifier
3. Build a narrow SoQL query
4. Cache and present the records

Example: A contractor can display recently issued building permits in a city.

Know this: Schemas, update schedules, limits, and data quality are controlled by each publishing agency.

🔗 Website · Developer docs

What it does: Stripe processes online and in-person payments, subscriptions, invoices, payouts, and marketplace transactions. Its hosted components reduce the amount of payment data a website handles.

How it works: The server creates a payment or checkout session using a secret key. Stripe securely collects payment details and sends status updates through redirects and webhooks.

How we'd add it to a customer's site:

1. Create and verify a Stripe account
2. Use Checkout or secure Elements
3. Create payments on the server
4. Verify webhooks before fulfilling orders

Example: A cleaning company can collect deposits when customers book service.

Know this: Transaction and optional product fees apply, and secret keys must never be exposed in browser code.

🔗 Website · Developer docs

What it does: Square supports online and in-person payments plus orders, catalog, customers, inventory, loyalty, and invoices. It can synchronize a website with a merchant's Square account.

How it works: The browser tokenizes payment information with Square's SDK and sends the token to the server. The server creates the payment, then receives JSON and webhook updates.

How we'd add it to a customer's site:

1. Create a Square developer app
2. Add the Web Payments SDK
3. Charge tokens through the backend
4. Validate webhooks and test refunds

Example: A bakery can take prepaid custom-cake orders on its website.

Know this: The APIs are free to integrate, but live payments incur processing fees and seller-country restrictions.

🔗 Website · Developer docs

What it does: They support PayPal checkout, cards, subscriptions, invoicing, payouts, and transaction reporting. Customers can pay with PayPal or other methods enabled for the merchant.

How it works: The server exchanges client credentials for an access token and creates an order. The buyer approves it, and the server captures payment and processes webhook updates.

How we'd add it to a customer's site:

1. Create a PayPal developer app
2. Add PayPal checkout buttons
3. Create and capture orders server-side
4. Verify webhooks before fulfillment

Example: A repair shop can accept online invoice payments through PayPal.

Know this: Merchant fees, country availability, account approval, and product-specific rules apply.

🔗 Website · Developer docs

What it does: Braintree processes cards, PayPal, Venmo, wallets, subscriptions, and marketplace-style payments. It provides client SDKs and a server gateway.

How it works: The server creates a client token while the browser securely collects and tokenizes payment details. The server sends the resulting nonce to Braintree to create a transaction.

How we'd add it to a customer's site:

1. Open and verify a merchant account
2. Install client and server SDKs
3. Tokenize payment details
4. Create transactions and handle webhooks

Example: A membership business can charge recurring dues and accept Venmo.

Know this: Processing fees and regional eligibility apply, and some capabilities require underwriting or approval.

🔗 Website · Developer docs

What it does: It exposes Calendly users, event types, scheduled events, invitees, routing forms, and webhooks. It helps websites connect scheduling activity with other business systems.

How it works: A backend uses OAuth or a personal access token to request JSON resources. Webhooks notify the website when invitees schedule or cancel.

How we'd add it to a customer's site:

1. Create a Calendly developer app
2. Authorize the business account
3. Link an event type or embed Calendly
4. Process scheduling webhooks

Example: A consultant can show booking options and record appointments in a CRM.

Know this: Available endpoints, webhooks, and administrative features can depend on the customer's Calendly plan.

🔗 Website · Developer docs

What it does: It searches availability and creates, reads, updates, or cancels appointments for Square sellers. It works with Square locations, customers, staff, and catalog services.

How it works: The backend uses a Square access token and calls JSON endpoints for profiles, availability, and bookings. OAuth permissions control buyer-level and seller-level actions.

How we'd add it to a customer's site:

1. Create a Square application
2. Onboard the seller to Appointments
3. Search availability
4. Create bookings and receive webhooks

Example: A salon can let visitors choose a stylist and available appointment time.

Know this: Seller-level write operations require eligible paid Appointments plans, while free plans support more limited buyer-level actions.

🔗 Website · Developer docs

What it does: It manages Acuity appointments, availability, calendars, clients, packages, forms, and appointment types. It can power a custom booking interface or synchronize other systems.

How it works: The backend authenticates and sends REST requests for availability or appointment actions. Responses return JSON, while webhooks report scheduling changes.

How we'd add it to a customer's site:

1. Subscribe to Acuity Scheduling
2. Create API or OAuth credentials
3. Query appointment types and availability
4. Create bookings and handle webhooks

Example: A massage therapist can offer a branded appointment chooser.

Know this: A paid Acuity subscription is required, and credentials must remain on the server.

🔗 Website · Developer docs

What it does: It exposes services, providers, schedules, clients, bookings, and related SimplyBook.me data. It supports custom appointment interfaces and business-system integrations.

How it works: The server obtains an authentication token and sends JSON-RPC requests. The API returns available slots or performs booking operations.

How we'd add it to a customer's site:

1. Create a SimplyBook.me account
2. Enable API access
3. Authenticate from the backend
4. Search slots and create bookings

Example: A tutoring center can let parents select a teacher and lesson time.

Know this: Plan limits, booking quotas, and enabled custom features affect what the integration can do.

🔗 Website · Developer docs

What it does: Twilio sends and receives SMS, MMS, WhatsApp messages, phone calls, verification codes, and other communications. It supplies phone numbers and programmable communications workflows.

How it works: A backend authenticates with Twilio credentials and posts message or call instructions to a REST API. Twilio contacts carriers and reports delivery or inbound events through webhooks.

How we'd add it to a customer's site:

1. Create a Twilio account
2. Obtain and verify a sender
3. Send from the backend
4. Validate status and inbound webhooks

Example: A dental office can send appointment reminders and accept text replies.

Know this: Production usage is metered, and U.S. messaging may require A2P 10DLC or toll-free verification.

🔗 Website · Developer docs

What it does: SendGrid sends transactional and marketing email and reports delivery, opens, clicks, bounces, and complaints. It also supports templates, contact lists, and email validation.

How it works: The backend posts email content or a template ID to the API with a secret key. SendGrid delivers the message and sends event data to a webhook.

How we'd add it to a customer's site:

1. Create a SendGrid account
2. Authenticate a sending domain
3. Create a restricted API key
4. Send email and process events

Example: An online retailer can send receipts and shipping updates.

Know this: The free access is limited or trial-based, and production delivery requires domain authentication and anti-spam compliance.

🔗 Website · Developer docs

What it does: Mailgun sends, receives, routes, and tracks transactional email. It includes validation, templates, suppression lists, logs, and delivery analytics.

How it works: A server submits a message through REST or SMTP using authenticated credentials. Mailgun delivers it and posts delivery, bounce, complaint, or inbound events to webhooks.

How we'd add it to a customer's site:

1. Create a Mailgun account
2. Verify the sending domain
3. Store the API key server-side
4. Send messages and process webhooks

Example: A property manager can email rent receipts and maintenance updates.

Know this: Free use is generally trial-limited, and ongoing production sending is paid.

🔗 Website · Developer docs

What it does: Resend is a developer-focused service for transactional and marketing email. It supports templates, batches, scheduling, inbound email, domains, and delivery events.

How it works: The backend posts recipients and content to a REST endpoint with an API key. Resend delivers the email and can send status events to a webhook.

How we'd add it to a customer's site:

1. Create an account
2. Verify the sending domain
3. Create a scoped API key
4. Send server-side and monitor events

Example: A contractor can send quote confirmations from the company's domain.

Know this: The free plan has daily, monthly, domain, and retention limits.

🔗 Website · Developer docs

What it does: They provide SMS, MMS, WhatsApp, voice calls, video, verification, and conversational messaging. Businesses can add programmable communications without operating carrier infrastructure.

How it works: A server sends authenticated API requests containing a destination and message or call instructions. Vonage routes the communication and reports status or inbound activity through webhooks.

How we'd add it to a customer's site:

1. Create a Vonage developer account
2. Obtain credentials and a sender
3. Call the API from the backend
4. Validate delivery and inbound webhooks

Example: A home-services company can text arrival notices and connect calls.

Know this: Trial credit is limited, production is usage-priced, and sender registration rules vary by country.

🔗 Website · Developer docs

What it does: It searches places and returns addresses, hours, ratings, reviews, photos, contact data, and other details. Places API (New) is the current recommended version.

How it works: A backend sends a search or place-detail request with an API key and field mask. Google returns JSON and bills according to the highest requested field category.

How we'd add it to a customer's site:

1. Enable Places API (New)
2. Restrict the API key
3. Find and store the place ID
4. Request only fields the page displays

Example: A hotel can show nearby restaurants with ratings and opening hours.

Know this: Billing is required, caching is restricted, and Google attribution and content-display rules apply.

🔗 Website · Developer docs

What it does: They manage authorized Google Business Profile locations, business information, reviews, posts, photos, verification, and performance data. They are intended for merchants and legitimate service providers managing profiles.

How it works: The business authorizes the application through OAuth 2.0. The backend uses the resulting token to read or change only profiles that user can access.

How we'd add it to a customer's site:

1. Create a Cloud project and organization account
2. Apply for basic API access
3. Implement merchant OAuth consent
4. Call the required profile APIs

Example: A local-marketing agency can display and respond to client reviews in a dashboard.

Know this: Access requires Google approval, quota may initially be zero, and the app cannot query arbitrary businesses.

🔗 Website · Developer docs

What it does: Formerly called Yelp Fusion, it supplies business search, details, ratings, review excerpts, photos, categories, and location data. It is designed for applications that incorporate Yelp place information.

How it works: The backend sends HTTPS requests with a bearer API key and search filters or a business ID. Yelp returns structured JSON business records.

How we'd add it to a customer's site:

1. Select a Yelp Places plan
2. Create an app and key
3. Search or request business details
4. Display required Yelp branding

Example: A tourism website can list nearby attractions and their Yelp ratings.

Know this: The free trial is evaluation-only, while commercial deployment requires a paid license and compliance with display rules.

🔗 Website · Developer docs

What it does: It searches points of interest and returns place names, categories, locations, hours, chains, and related attributes. Foursquare's newer endpoints are powered by FSQ OS Places.

How it works: A server sends an authenticated request with text, coordinates, categories, or a place identifier. The API responds with structured JSON place data.

How we'd add it to a customer's site:

1. Create a developer project
2. Generate an API key
3. Search around the customer's location
4. Cache permitted fields and show attribution

Example: A shopping district can publish a searchable directory of nearby businesses.

Know this: Only a small number of higher-value calls are free, and endpoint pricing and attribution rules vary.

🔗 Website · Developer docs

What it does: It reads YouTube videos, channels, playlists, comments, captions, and search results. Authorized operations can also manage a user's YouTube resources.

How it works: Public-data calls use an API key, while account actions use OAuth 2.0. REST endpoints return JSON and consume units from a daily project quota.

How we'd add it to a customer's site:

1. Create a Google Cloud project
2. Enable YouTube Data API v3
3. Create restricted credentials
4. Fetch and embed approved content

Example: A gym can automatically list its latest workout videos.

Know this: The default daily quota is limited, search calls are comparatively expensive, and YouTube policies apply.

🔗 Website · Developer docs

What it does: It accesses permitted Facebook Page data and powers Instagram API integrations, including Instagram API with Instagram Login. Capabilities include profiles, media, comments, insights, publishing, and messaging where approved.

How it works: A business user authorizes a Meta app and grants specific permissions. The backend sends versioned Graph requests with access tokens and receives JSON or webhook events.

How we'd add it to a customer's site:

1. Create a Meta developer app
2. Add the required Facebook or Instagram product
3. Implement login and token storage
4. Request review for advanced permissions

Example: A restaurant can show recent Instagram posts and publish approved content.

Know this: Most business capabilities require eligible accounts, app review, permission approval, and ongoing policy compliance.

🔗 Website · Developer docs

What it does: It manages authorized Pinterest boards, Pins, catalogs, shopping data, ads, and analytics. It supports integrations that publish content or report Pinterest performance.

How it works: A Pinterest user authorizes the app through OAuth. The backend sends bearer-token requests and receives JSON resources and metrics.

How we'd add it to a customer's site:

1. Create a Pinterest developer app
2. Implement OAuth
3. Request needed scopes and approval
4. Create Pins or read analytics

Example: A furniture store can publish product Pins from its website catalog.

Know this: Production access and advertising permissions may require app review and adherence to Pinterest's content rules.

🔗 Website · Developer docs

What it does: The Display API reads an authorized creator's profile and public videos. The Content Posting API uploads drafts or publishes authorized video and photo posts.

How it works: The creator signs in and grants requested OAuth scopes to the app. The backend uses the access token to list content or initialize, upload, and monitor a post.

How we'd add it to a customer's site:

1. Register a TikTok app
2. Add Login Kit and required APIs
3. Implement creator authorization
4. Pass review and handle post status

Example: A video studio can let clients approve and publish finished clips to TikTok.

Know this: Public direct posting requires an audit, while unaudited clients have private-only and user limits.

🔗 Website · Developer docs

What it does: LinkedIn APIs support sign-in, member-authorized posting, organization pages, marketing, advertising, and talent products. Access depends heavily on the approved LinkedIn program and permissions.

How it works: A member or administrator grants OAuth permission to an approved application. The backend uses access tokens to call JSON endpoints for the allowed product.

How we'd add it to a customer's site:

1. Create a LinkedIn application
2. Request the correct product access
3. Implement OAuth and secure tokens
4. Publish or read only approved data

Example: A law firm can publish approved company updates from its website dashboard.

Know this: Many useful permissions require partner approval, app review, or an eligible organization relationship.

🔗 Website · Developer docs

What it does: It creates and manages Google Ads campaigns, budgets, keywords, audiences, assets, and reports. Agencies can automate work across linked advertising accounts.

How it works: The application uses OAuth, a developer token, and customer account identifiers. Requests go through client libraries or gRPC and return structured campaign data.

How we'd add it to a customer's site:

1. Create a manager account
2. Apply for a developer token
3. Configure OAuth credentials
4. Test before managing live campaigns

Example: A marketing agency can automatically generate weekly ad-performance dashboards.

Know this: API access is free, but ads cost money and production use requires an approved developer token.

🔗 Website · Developer docs

What it does: It manages Meta ad accounts, campaigns, ad sets, ads, audiences, creatives, and reporting. It covers advertising across Facebook, Instagram, Messenger, and supported placements.

How it works: An authorized business user grants permissions to a Meta app. The backend calls versioned Graph endpoints with access tokens and receives JSON results.

How we'd add it to a customer's site:

1. Create a Meta business app
2. Connect the ad account
3. Request ads permissions and review
4. Create reports or manage campaigns

Example: An agency can show a client its leads, spend, and cost per result.

Know this: The API is free, but advertising spend, app review, business verification, and rate limits apply.

🔗 Website · Developer docs

What it does: It manages Microsoft Advertising campaigns and downloads performance reports. Supported inventory can include Bing, AOL, Yahoo, and Microsoft audience placements.

How it works: The application obtains OAuth tokens and uses a developer token with SOAP or REST services. The APIs return account, campaign, bulk, or report data.

How we'd add it to a customer's site:

1. Open a Microsoft Advertising account
2. Request a developer token
3. Register an OAuth application
4. Use sandbox before production

Example: A local agency can combine Bing campaign results with its client dashboard.

Know this: API use is free, but ads are paid and account, token, and consent requirements apply.

🔗 Website · Developer docs

What it does: It reads and publishes posts, searches content, manages users, and accesses engagement or streaming data according to plan. Available endpoints and volume vary substantially by access tier.

How it works: An application authenticates with app credentials or user OAuth tokens. It sends REST or streaming requests and receives JSON posts, users, metrics, or events.

How we'd add it to a customer's site:

1. Create an X developer project
2. Choose an access plan
3. Implement the required OAuth flow
4. Call approved endpoints and monitor usage

Example: A venue can publish event announcements from its content dashboard.

Know this: Useful production access is paid and governed by strict quotas, automation rules, and content policies.

🔗 Website · Developer docs

What it does: It provides models for text, reasoning, images, speech, transcription, embeddings, realtime interaction, and tool use. Developers can build assistants, search tools, content workflows, and multimodal features.

How it works: A backend sends prompts and inputs to authenticated REST, streaming, or realtime endpoints. The model returns generated content or structured tool calls, with usage billed by the selected model.

How we'd add it to a customer's site:

1. Create a platform project and key
2. Keep the key on the server
3. Call the Responses API
4. Add moderation, limits, and human review

Example: A contractor can turn customer notes into a draft project estimate.

Know this: Usage is metered, outputs can be wrong, and sensitive or high-impact workflows need safeguards.

🔗 Website · Developer docs

What it does: It provides Claude models for writing, analysis, coding, vision, document work, and tool use. Features include streaming, prompt caching, batches, files, and server-side tools.

How it works: The backend sends messages and optional tools to the API using a secret key. Claude returns text or structured tool requests, and usage is measured in tokens and feature calls.

How we'd add it to a customer's site:

1. Create a Console account
2. Generate a server-side API key
3. Call the Messages API
4. Add limits and review important outputs

Example: An accountant can summarize uploaded policy documents for clients.

Know this: Small introductory credits may be available, but ongoing production usage is metered.

🔗 Website · Developer docs

What it does: It provides Gemini models for text, images, audio, video, structured output, tools, embeddings, and realtime interaction. Google AI Studio supports quick prototyping and key management.

How it works: The application sends multimodal input to REST or an official SDK using an API key. Gemini returns generated content, structured data, or tool calls.

How we'd add it to a customer's site:

1. Create a key in Google AI Studio
2. Choose a model and SDK
3. Call the API from the backend
4. Apply safety settings and quotas

Example: A repair company can analyze a customer photo and draft intake questions.

Know this: Free-tier model availability and rate limits vary, and paid use requires Cloud Billing.

🔗 Website · Developer docs

What it does: It generates speech, sound effects, music, dubbing, voice transformations, and conversational voice agents. It also offers speech recognition and voice-management features.

How it works: A backend sends text, audio, or agent instructions with an API key. The service returns audio streams, files, transcripts, or conversation events.

How we'd add it to a customer's site:

1. Create an account and key
2. Choose an allowed voice or model
3. Generate audio from the backend
4. Cache files and disclose synthetic voice use

Example: A tour company can add natural spoken narration to destination pages.

Know this: Credits and voice features vary by plan, and cloned voices require consent and policy compliance.

🔗 Website · Developer docs

What it does: It transcribes recorded or streaming audio and can add speaker labels, chapters, summaries, sentiment, and content detection. It is designed for speech-intelligence applications.

How it works: The backend uploads audio or supplies a reachable URL and starts a transcript job. The service processes it asynchronously and returns JSON or sends completion webhooks.

How we'd add it to a customer's site:

1. Create an account and API key
2. Upload or securely host audio
3. Submit a transcription request
4. Poll or handle the completion webhook

Example: A sales trainer can turn recorded calls into searchable transcripts.

Know this: Free credits are limited, and customer recordings require appropriate consent and privacy handling.

🔗 Website · Developer docs

What it does: It generates and edits images, video, audio, and 3D assets using Stability AI models. Image tools include text generation, inpainting, upscaling, and background operations.

How it works: A backend sends a prompt and optional source image with an API key. The selected model consumes credits and returns a generated asset or result data.

How we'd add it to a customer's site:

1. Create a platform account
2. Generate an API key
3. Call a suitable generation endpoint
4. Store and review returned assets

Example: A florist can generate seasonal banner concepts for its website.

Know this: The introductory credits are finite, later requests consume paid credits, and outputs require rights review.

🔗 Website · Developer docs

What it does: It detects languages and translates text, documents, websites, and customized terminology. Advanced editions add glossaries, document translation, and adaptive features.

How it works: A backend sends source content and target-language codes with authenticated Google Cloud credentials. The service returns translated text or a processed document.

How we'd add it to a customer's site:

1. Create a Cloud project
2. Enable Translation and billing
3. Authenticate a service account
4. Translate server-side and cache results

Example: A clinic can offer translated versions of its general service pages.

Know this: A monthly free allowance exists, but usage beyond it is billed and critical translations need human review.

🔗 Website · Developer docs

What it does: It translates text and documents and supports glossaries, language detection, and writing improvements. It is known for high-quality translation across supported languages.

How it works: The backend posts text, documents, language codes, and an authentication key. DeepL returns translated content and usage information.

How we'd add it to a customer's site:

1. Create a DeepL API account
2. Store the authentication key server-side
3. Send text or documents
4. Cache translations and add human review

Example: A restaurant can maintain English and Spanish menu pages.

Know this: API Free has a monthly character cap, while more volume and some features require API Pro.

🔗 Website · Developer docs

What it does: It translates text and documents, detects languages, transliterates scripts, and manages custom terminology. It supports many languages through Azure AI services.

How it works: A backend sends content and target languages with an Azure key or token. The service returns translated JSON or processed document files.

How we'd add it to a customer's site:

1. Create an Azure Translator resource
2. Store the key and region securely
3. Call text or document translation
4. Cache and review translations

Example: A hotel can translate booking instructions into guests' preferred languages.

Know this: The free tier has a monthly character limit, and higher usage is billed.

🔗 Website · Developer docs

What it does: They provide USPS addresses, rates, service standards, tracking, labels, locations, and shipping functions. The newer USPS Developer Portal uses modern REST APIs and OAuth.

How it works: A registered application obtains an OAuth access token and sends shipment or lookup data to an endpoint. USPS returns structured rate, address, label, or tracking data.

How we'd add it to a customer's site:

1. Register in the USPS Developer Portal
2. Create an application
3. Implement OAuth
4. Test the selected shipping APIs

Example: A gift shop can quote USPS rates and show package tracking.

Know this: Production access may require a USPS business relationship, and mailpiece and label rules must be followed.

🔗 Website · Developer docs

What it does: They provide rates, shipping labels, addresses, pickup, locations, transit times, and package tracking. They connect websites directly with UPS shipping services.

How it works: A backend obtains OAuth credentials and sends shipment or tracking requests. UPS returns JSON containing rates, labels, validation results, or status events.

How we'd add it to a customer's site:

1. Create a UPS account and app
2. Obtain OAuth credentials
3. Test rate and shipping requests
4. Store labels and tracking securely

Example: A parts supplier can compare UPS services and print a label after checkout.

Know this: API access is free, but shipping costs apply and some services require an eligible UPS account.

🔗 Website · Developer docs

What it does: They provide rates, transit times, address validation, shipping labels, pickup, locations, and tracking. FedEx also offers paid advanced visibility products.

How it works: A backend exchanges credentials for an OAuth token and submits shipment or tracking requests. FedEx returns JSON with rates, labels, or shipment status.

How we'd add it to a customer's site:

1. Create a FedEx organization and project
2. Associate a FedEx account
3. Test selected APIs
4. Complete any required label validation

Example: A machine shop can quote FedEx delivery and generate shipping labels.

Know this: Core APIs are free, but transportation costs apply and third-party solutions may require FedEx validation.

🔗 Website · Developer docs

What it does: EasyPost provides a common API for carrier rates, labels, tracking, addresses, insurance, and returns. It reduces the need to build separate integrations for each carrier.

How it works: The backend sends parcel and address data using an API key. EasyPost returns normalized carrier rates, purchased labels, and tracking events as JSON.

How we'd add it to a customer's site:

1. Create an account and wallet
2. Add carrier accounts or use EasyPost rates
3. Create a shipment and select a rate
4. Buy the label and handle tracking

Example: A boutique can compare carriers and print the cheapest suitable label.

Know this: Testing is free, but labels, postage, insurance, and usage beyond included allowances can cost money.

🔗 Website · Developer docs

What it does: Shippo combines carrier rates, labels, tracking, addresses, customs, manifests, and returns behind one API. It supports Shippo's discounted rates and connected carrier accounts.

How it works: The backend sends shipment dimensions and addresses with an API token. Shippo returns normalized rates, then creates labels and tracking records after purchase.

How we'd add it to a customer's site:

1. Create a Shippo account
2. Generate a private token
3. Create a shipment and compare rates
4. Purchase a label and process tracking

Example: A craft seller can offer live shipping choices during checkout.

Know this: Postage always costs money, and platform fees or plan limits can apply to production labels.

🔗 Website · Developer docs

What it does: It supplies U.S. property characteristics, ownership, mortgages, sales, assessments, valuations, schools, and neighborhood data. Coverage spans more than 150 million properties.

How it works: A backend sends an address, parcel identifier, or geographic query with an API key. The service returns JSON or XML property records.

How we'd add it to a customer's site:

1. Create a trial developer account
2. Choose licensed data packages
3. Query by address or parcel
4. Cache and label the returned fields

Example: A real-estate agent can show property facts and recent sale history.

Know this: The free access is trial-limited, production data is licensed, and display rights vary by field.

🔗 Website · Developer docs

What it does: It provides U.S. property records, rental estimates, value estimates, market statistics, and active listings. It is designed for real-estate and rental applications.

How it works: A backend sends an address, coordinates, or market filters with an API key. RentCast returns normalized JSON property, listing, or estimate data.

How we'd add it to a customer's site:

1. Create a RentCast account
2. Copy the API key
3. Choose a property or market endpoint
4. Cache and display relevant results

Example: A property manager can show an estimated market rent for a house.

Know this: The free plan allows only 50 requests per month, and estimates are not formal appraisals.

🔗 Website · Developer docs

What it does: It provides U.S. parcel boundaries and standardized property attributes. Searches can use coordinates, addresses, parcel numbers, owners, or geographic shapes.

How it works: The backend sends a token and parcel search to Regrid's API. Results arrive as GeoJSON feature collections containing geometry and property fields.

How we'd add it to a customer's site:

1. Create a developer account and token
2. Choose a narrow parcel lookup
3. Set a low result limit
4. Cache permitted results for up to 30 days

Example: A fencing contractor can display the parcel outline for a customer's address.

Know this: Trial access is limited, billing counts returned parcels, and repeated requests are billed again.

🔗 Website · Developer docs

What it does: It returns Walk Score, Transit Score, Bike Score, descriptions, and nearby-location links where available. The scores summarize access to amenities and transportation.

How it works: A server-side script sends an address, coordinates, and API key. The service returns JSON or XML score data for display.

How we'd add it to a customer's site:

1. Apply for an API key
2. Geocode the property accurately
3. Call the API from the server
4. Display the score with required branding

Example: An apartment website can show how walkable each listing's neighborhood is.

Know this: Free features and volume are limited, premium use requires pricing approval, and browser-side calls are not allowed.

🔗 Website · Developer docs

What it does: It decodes VINs and provides vehicle, manufacturer, make, model, plant, and specification information. Data comes largely from manufacturer submissions to NHTSA.

How it works: A client sends a VIN or vehicle query to a public endpoint. The API returns JSON, XML, CSV, or other supported formats without registration.

How we'd add it to a customer's site:

1. Collect a VIN or vehicle selection
2. Call the appropriate vPIC method
3. Validate the returned model year
4. Display decoded fields

Example: An auto shop can decode a customer's VIN before requesting service.

Know this: It is free and has no daily quota, but automated traffic controls apply and older VIN coverage is less reliable.

🔗 Website · Developer docs

What it does: It searches foods and returns nutrients, ingredients, portions, branded products, and data-source information. It combines USDA reference, survey, foundation, and branded-food datasets.

How it works: A backend sends a food search or food identifier with a data.gov API key. The service returns structured JSON food and nutrient records.

How we'd add it to a customer's site:

1. Request a data.gov API key
2. Search for a food
3. Retrieve the selected food details
4. Normalize serving sizes before display

Example: A meal-prep business can calculate nutrition facts for menu ingredients.

Know this: Rate limits apply, and branded-food values and serving sizes require careful interpretation.

🔗 Website · Developer docs

What it does: It provides crowdsourced packaged-food barcodes, ingredients, nutrition, allergens, labels, and product images. The database is open and covers products from many countries.

How it works: A client queries a barcode or search endpoint and receives JSON product records. Authorized contributors can also submit product updates and images.

How we'd add it to a customer's site:

1. Read the API and reuse terms
2. Add barcode or text search
3. Cache products and images responsibly
4. Show source attribution and missing-data warnings

Example: A grocery store can let shoppers scan products for allergen information.

Know this: Data is community-contributed and incomplete, so it must not be treated as guaranteed medical guidance.

🔗 Website · Developer docs

What it does: They analyze recipes and ingredients for nutrition, diets, health labels, and food data. Related APIs provide recipe search and meal-planning information.

How it works: A backend sends ingredient text or a recipe using an application ID and key. Edamam returns structured JSON nutrients, quantities, and labels.

How we'd add it to a customer's site:

1. Create a developer application
2. Store the ID and key securely
3. Submit normalized ingredient lines
4. Display nutrients with attribution

Example: A caterer can provide estimated calories and dietary labels for dishes.

Know this: The free developer plan has strict limits and licensing restrictions, while commercial use needs a paid plan.

🔗 Website · Developer docs

What it does: It supplies recipes, ingredients, nutrition, menus, products, meal planning, and food-related analysis. It can search by diet, intolerance, cuisine, or available ingredients.

How it works: A backend sends search or analysis parameters with an API key. Spoonacular returns JSON and deducts points based on the endpoint's cost.

How we'd add it to a customer's site:

1. Create an account and API key
2. Choose a low-cost endpoint
3. Call it from the backend
4. Cache and attribute displayed data

Example: A cooking school can suggest recipes based on ingredients students already have.

Know this: The free daily point allowance is small, and some endpoints consume multiple points per request.

🔗 Website · Developer docs

What it does: It searches earthquake events by time, location, magnitude, depth, and other parameters. USGS also publishes ready-made real-time GeoJSON feeds.

How it works: A website or backend calls a query URL or downloads a feed. The service returns GeoJSON, JSON, CSV, XML, or other supported formats.

How we'd add it to a customer's site:

1. Choose a live feed or query
2. Limit the geographic area
3. Cache and plot events
4. Link to the official event page

Example: A property-inspection company can show recent earthquakes in its region.

Know this: Preliminary earthquake details can change as USGS analysts revise an event.

🔗 Website · Developer docs

What it does: It provides decades of U.S. consumer-product recall records. Fields include products, companies, hazards, recall dates, descriptions, countries, and UPCs when available.

How it works: A client queries CPSC's recall web service using supported filters. The service returns machine-readable recall records for processing or display.

How we'd add it to a customer's site:

1. Review the recall service documentation
2. Query by product or company
3. Cache results with recall dates
4. Link users to the official notice

Example: A resale shop can flag products matching current recall records.

Know this: Product identifiers are not always present or standardized, so automated matches need human confirmation.

🔗 Website · Developer docs

What it does: It returns vehicle, tire, equipment, and child-seat recall information. Vehicle searches can use model year, make, model, or NHTSA campaign number.

How it works: A client submits vehicle details or a campaign number to a public endpoint. The API returns JSON recall records and official campaign information.

How we'd add it to a customer's site:

1. Collect year, make, and model
2. Call the recall endpoint
3. Present campaign and remedy details
4. Link to NHTSA for confirmation

Example: An auto dealer can show recalls for a selected used vehicle model.

Know this: It is not intended for bulk VIN lookups, and a model-level result does not prove a specific vehicle is affected.

🔗 Website · Developer docs

What it does: It provides public FDA data on drugs, devices, foods, adverse events, labels, enforcement, and recalls. Search and aggregation endpoints support structured analysis.

How it works: A client sends a search expression and optional free API key to a dataset endpoint. The service returns JSON records or aggregated counts.

How we'd add it to a customer's site:

1. Choose the correct FDA dataset
2. Register for a free key
3. Build a narrow search query
4. Display disclaimers and official links

Example: A pharmacy website can show recent FDA drug-enforcement notices.

Know this: The data is not medical advice, reports do not prove causation, and requests are rate-limited.

🔗 Website · Developer docs

What it does: It searches articles and retrieves top headlines from a large collection of news sources. Results include metadata, excerpts, images, sources, and links rather than full articles.

How it works: A backend sends keywords, dates, sources, or categories with an API key. The service returns JSON article summaries and original URLs.

How we'd add it to a customer's site:

1. Create an API key
2. Build a focused server-side query
3. Cache results within license terms
4. Link to the original publishers

Example: A financial adviser can show headlines about markets and interest rates.

Know this: The free plan is development-only with delayed news, while published commercial websites require a paid plan.

🔗 Website · Developer docs

What it does: It searches news and provides top headlines from international sources. Paid plans add real-time articles, deeper history, full content, and larger quotas.

How it works: The backend sends a query or headline category with an API key. GNews returns JSON articles containing source information, text fields, images, and URLs.

How we'd add it to a customer's site:

1. Create an account and key
2. Call Search or Top Headlines
3. Cache and deduplicate stories
4. Link and credit the source

Example: A chamber of commerce can show headlines about its city and local industries.

Know this: The free plan is non-commercial, delayed by 12 hours, limited to 100 daily requests, and blocked by CORS on deployed sites.

🔗 Website · Developer docs

What it does: It searches Guardian articles, sections, tags, editions, and an archive dating to 1999. Depending on the license, responses can include article text and media.

How it works: A backend submits search parameters and an API key to the content endpoint. The service returns JSON metadata and licensed fields.

How we'd add it to a customer's site:

1. Register for the correct key
2. Search by tag or phrase
3. Cache within license terms
4. Display required links and attribution

Example: A bookshop can show Guardian articles about new literary releases.

Know this: Free keys are limited to non-commercial use, while any commercial website needs a commercial agreement.

🔗 Website · Developer docs

What it does: They provide NYT article search, archives, top stories, most-popular stories, books, reviews, and other datasets. Available fields depend on the selected API.

How it works: A backend calls a product endpoint with a registered API key and query parameters. The service returns JSON metadata and links to NYT content.

How we'd add it to a customer's site:

1. Create an NYT developer account
2. Register an application
3. Call the required API
4. Cache responsibly and show attribution

Example: A bookstore can display current New York Times best-seller lists.

Know this: Per-minute and daily limits apply, and NYT content must be displayed under its branding and usage rules.

🔗 Website · Developer docs

What it does: It provides stock, option, forex, cryptocurrency, commodity, economic, technical-indicator, and market-news data. Responses are available as JSON or CSV.

How it works: A backend sends a function name, symbol, interval, and API key. Alpha Vantage returns the requested time series or analysis subject to plan limits.

How we'd add it to a customer's site:

1. Request an API key
2. Choose a documented function
3. Call it from the backend
4. Cache results and label delays

Example: A financial planner can display a small watchlist of market prices.

Know this: The free request rate is low, some data is delayed or premium, and it is not an exchange-grade trading feed.

🔗 Website · Developer docs

What it does: It supplies stock, forex, crypto, company, earnings, economic, alternative, and market-news data. REST and WebSocket interfaces support snapshots and streaming.

How it works: A backend or secured streaming client authenticates with an API token and requests symbols or datasets. Finnhub returns JSON or pushes WebSocket market updates.

How we'd add it to a customer's site:

1. Create an account and token
2. Choose licensed market endpoints
3. Call from a secured backend
4. Cache and label data timing

Example: An investment newsletter can show company news and basic quote data.

Know this: Free data has strict limits and licensing constraints, while real-time exchange data may require paid access.

🔗 Website · Developer docs