Business apps and their data APIs
Workplace and advertising apps — the campaign, payroll, scheduling and employee self-service APIs behind business operations.
Business apps here serve two constituencies: employees and advertisers. ADP Mobile Solutions is the employee self-service client — after POST /v1/session/login it serves pay statements, time-off and profile data over GraphQL — and MyWalmart covers the associate side of the world's largest retailer through a set of /v1/graphql/associate operations for schedule, paystub and attendance.
On the advertiser side, Meta Ads Manager wraps campaign management — POST /v1/ads/campaigns, insights and performance charts, billing accounts and drafts — while Meta Business Suite covers the organic surface: page assets, content posts, inbox threads and lead cards. All four gate every call on an enterprise session token.
Frequently asked questions
Which employee self-service APIs are covered?
ADP Mobile Solutions exposes payroll, time-off and profile data through authenticated GraphQL operations after session login; MyWalmart serves associates their schedule, paystub and attendance records through /v1/graphql/associate operations. Both require an employer-issued account.
What can the Meta business apps' APIs do?
Meta Ads Manager manages the paid side: create and edit campaigns, pull insights and performance charts, read billing account state and check account standing. Meta Business Suite covers the organic side: page assets, post publishing, unified inbox threads and lead-card retrieval.
Do these apps share an auth pattern?
All four are session-token based: ADP uses a login call that mints a session, the Meta apps ride the Facebook/Meta account session, and MyWalmart authenticates the associate identity before any GraphQL operation. No anonymous access exists on these surfaces.
