tuples-api-best-practices.mdx

title	description	sidebar_position	slug
Managing Tuples and Invoking API Best Practices	Best Practices of Managing Tuples and Invoking APIs	8	/getting-started/tuples-api-best-practices

import { DocumentationNotice, ProductName, ProductNameFormat, RelatedSection, } from "@components/Docs";

Best Practices of Managing Tuples and Invoking APIs

The following list outlines some guidelines and best practices for using :

• Do not store Personal Identifiable Information in tuples
• Always specify authorization model ID whenever possible

Do Not Store Personal Identifiable Information in Tuples

You can use any string for user and object identifiers, however you should not input or assign identifiers that include Personal Data or any other sensitive data, such as data that may be restricted under regulatory requirements.

:::caution Note The documentation and samples uses first names and simple ids to illustrate easy-to-follow examples. :::

Always Specify Authorization Model ID Whenever Possible

It is strongly recommended that authorization model ID be specified in your Relationship Queries (such as Check and ListObjects) and Relationship Commands (such as Write).

Specifying authorization model ID in API calls have the following advantages:

1. Better performance as will not need to perform a database query to get the latest authorization model ID.
2. Allows consistent behavior in your production system until until you are ready to switch to the new model.

Related Sections

<RelatedSection description="Check the following sections for more on recommendation for managing relations and model in production environment." relatedLinks={[ { title: 'Migrating Relations', description: 'Learn how to migrate relations in a production environment', link: '../modeling/migrating/migrating-relations', id: '../modeling/migrating/migrating-relations', } ]} />