Skip to Content

ReceivedTokenResponseSchema

const ReceivedTokenResponseSchema: ZodObject<{ api: ZodOptional<ZodObject<{ links: ZodOptional<ZodRecord<ZodString, ZodObject<{ href: ZodString; }, $strip>>>; redactions: ZodOptional<ZodArray<ZodObject<{ path: ZodString; reason: ZodEnum<{ internal: ...; secret: ...; }>; }, $strip>>>; }, $strip>>; client: ZodNullable<ZodObject<{ device: ZodNullable<ZodString>; id: ZodEnum<{ "modem-cli": "modem-cli"; }>; }, $strip>>; createdAt: ZodISODateTime; expiresAt: ZodNullable<ZodISODateTime>; id: ZodUUID; lastUsedAt: ZodNullable<ZodISODateTime>; modes: ZodArray<ZodString>; name: ZodString; object: ZodLiteral<"admin_api_key">; owner: ZodObject<{ email: ZodNullable<ZodString>; id: ZodUUID; name: ZodNullable<ZodString>; }, $strip>; permissions: ZodArray<ZodString>; previousSecretExpiresAt: ZodNullable<ZodISODateTime>; projects: ZodUnion<readonly [ZodLiteral<"all">, ZodArray<ZodUUID>]>; rotatedAt: ZodNullable<ZodISODateTime>; secret: ZodString; secretPreview: ZodString; }, $strip>;

The token response as a client reads it. The code is spent once the server answers, so a permission or mode that a newer server added must not stop the secret arriving.

Last updated on