UPupsmith
admin
lsa-admin

Google Lsa Write Access

Whether the org's Google Ads credential can actually reply on its LSA lead conversations.

A read-only OAuth grant still reads leads (it holds ACCESS_GLS_LEAD), so ingestion looks healthy while every AppendLocalServicesLeadConversation is rejected. This reads customer_user_access per active account and reports whether any user holds ADMIN or STANDARD — telling those two states apart without attempting a write.

Accounts served by a mapped MCC manager credential report manager_served with no Google call. ok is false only for states a person must fix; a transient probe failure leaves it true. Read-only; one Google Ads op per non-manager-served account, cached 24h per org (use_cache=false forces a fresh read).

get/admin/lsa/write-access

Request

  • Base URL
    https://api-docs.upsmith.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header x-api-key
    • or HTTP bearer

Query parameters

organization_idstring required
use_cacheboolean

Headers

organization-idstring nullable
timezonestring
x-user-idstring nullable
x-actor-emailstring nullable
x-request-sourcestring nullable
x-operation-idstring nullable
x-commit-messagestring nullable
x-confirmation-idstring nullable
x-chat-idstring nullable

Response

Successful Response

organization_idstring required
okboolean required
reason'ok' | 'no_accounts' | 'no_write_access' | 'no_credential' | 'permission_denied' | 'account_not_found' | 'rate_limited' | 'provider_unavailable' required
checked_atstring date-time nullable

When this answer was actually obtained from Google (not when it was served).

Changes

No recorded changes to this operation across all 1 revision of this API.