[{"_id":"project-settings","settings":{"translateMetaTags":true,"translateAriaLabels":true,"translateTitle":true,"showWidget":true,"customWidget":{"theme":"light","font":"rgb(0, 0, 0)","header":"rgb(255, 255, 255)","background":"rgba(255, 255, 255,0.8)","position":"right","positionVertical":"center","border":"rgb(163, 163, 163)","borderRequired":true,"widgetCompact":true},"widgetLanguages":[{"code":"de","name":"Deutsch"},{"code":"fr","name":"Français"}],"activeLanguages":{"fr":"Français","de":"Deutsch","en":"English"},"enabledLanguages":["de","en","fr"],"debugInfo":false,"displayBranding":false,"displayBrandingName":false,"localizeImages":false,"localizeImagesLimit":false,"localizeAudio":false,"localizeAudioLimit":false,"localizeDates":false,"disabledPages":[],"regexPhrases":[{"phrase":"#1 of <var total-count=\"\"></var>","candidate":"#1 of ","variables":["<var total-count=\"\"></var>"],"regex":"^#1 of ([\\d ]+)$"},{"phrase":"#Jump to <var time-in-video=\"\"></var> in this episode","candidate":"#Jump to ","variables":["<var time-in-video=\"\"></var>"],"regex":"^#Jump to (.+?) in this episode$"}],"allowComplexCssSelectors":false,"blockedClasses":false,"blockedIds":false,"phraseDetection":true,"customDomainSettings":[],"seoSetting":[],"translateSource":false,"overage":false,"detectPhraseFromAllLanguage":false,"googleAnalytics":true,"mixpanel":false,"heap":false,"blockedComplexSelectors":[]},"version":59144},{"_id":"en","source":"en","pluralFn":"return n != 1 ? 1 : 0;","pluralForm":2,"dictionary":{},"version":59144},{"_id":"outdated","outdated":{"#Accéder à l'URL d'origine":1,"#Pour des raisons de sécurité lorsque vous utilisez Google Traduction, n'envoyez pas d'informations dans ce type de formulaire.":1,"#Formulaire non accepté":1,"#The role and potential that AI plays in solving personalization":1,"#About the current challenges in personalization through the lens of the CMS industry":1,"#Join the webinar to learn":1,"#Throughout the discussion, they will examine the current hurdles brands face in implementing personalization, how AI is revolutionizing the approach to solving these challenges, and the trends shaping the future of the CMS space.":1,"#This webinar will feature a dynamic fireside chat with <strong ljsid-1=\"\">Chuck Gahun, a Principal Analyst at Forrester, and Gurdeep Dhillon, the Chief Marketing Officer at Contentstack</strong> as they dive deep into the world of AI-powered personalization within the CMS industry.":1,"#Learn how AI is revolutionizing personalization in the CMS":1,"#September 25, 2024 @ 7 am PT / 10 pm ET / 4 pm CET":1,"#Forrester on Personalization":1,"#Webinar | Forrester on Personalization":1,"#Principal Analyst":1,"#Chuck Gahun":1,"#Strategic insights from experts for implementing AI-powered personalization":1,"#Webinar | Forrester on Personalization | Contentstack":1,"#Sagittarius is a Contentstack Solutions Partners | Contentstack":1,"#Nagarro is a Contentstack Solutions Partners | Contentstack":1,"#Create New JSON RTE Plugin In this guide, we will learn how to develop a new JSON Rich Text Editor plugin from the ground up. Note: When working within specific branches, plugins added or created will be available only within that particular branch. For example, you are working within the development branch, and you add new JSON RTE Plugins to this branch. These JSON RTE plugins will be available only within the development branch. Refer to our Branch-specific Modules document for more information. Prerequisites Node.js version 8 or above Building Your JSON RTE Plugin Here is an overview of th":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">1</strong></span> results for <strong ljsid-3=\"\">elementType</strong>":1,"#Klicken Sie im <span ljsid-1=\"\">Modus</span> <strong ljsid-3=\"\">„Cookies“</strong> auf der Registerkarte „ <strong ljsid-5=\"\">Cookies</strong> <span ljsid-7=\"\"><strong ljsid-7-0=\"\">Verwalten</strong></span> “ unten links auf die <strong ljsid-9=\"\">Domains-Zulassungsliste</strong> .":1,"#Domains-Zulassungsliste":1,"#Modus":1,"#Wir haben unsere Postman-Sammlung auch auf <a ljsid-1=\"\">GitHub</a> gehostet. Sie können die in der <a ljsid-3=\"\">Liesmich-</a> Datei genannten Schritte befolgen, um es herunterzuladen und zu verwenden.":1,"#Geben Sie im resultierenden <strong ljsid-1=\"\">Fork-Sammlungsmodalitäten</strong> bei Bedarf eine <strong ljsid-3=\"\">Gabel-Bezeichnung</strong> ein, mit der Sie Ihre Sammlung eindeutig identifizieren und einen <strong ljsid-5=\"\">Arbeitsplatz</strong> auswählen können.":1,"#Dadurch wird die <strong ljsid-1=\"\">Gabel-Sammlung in Ihrem Arbeitsbereich</strong> geöffnet, von wo aus Sie die Contentstack Postman-Sammlung auf die folgenden drei Arten herunterladen bzw. damit arbeiten können:":1,"#Postman ist für <a ljsid-1=\"\">Windows (x32)</a>, <a ljsid-3=\"\">Windows (x64)</a>, Mac ( <a ljsid-5=\"\">Intel-Chip</a> / <a ljsid-7=\"\">Apple-Chip</a> ) und <a ljsid-9=\"\">Linux-</a> Umgebungen verfügbar.":1,"#Um die Contentstack Postman-Sammlung nutzen zu können, benötigen Sie den <a ljsid-1=\"\">Briefträger</a> . Sie können entweder die <strong ljsid-3=\"\">Desktop-App</strong> herunterladen oder <strong ljsid-5=\"\">Postman for Web</strong> verwenden.":1,"#Die Contentstack Postman-Sammlung besteht aus einer Reihe vorkonfigurierter REST-API-Anfragen, die Ihnen den Einstieg in die <a ljsid-1=\"\">Contentstack-APIs</a> und das Ausprobieren unserer API-Anfragen über den beliebten <a ljsid-3=\"\">Briefträger-</a> REST-Client erleichtern.":1,"#Versagen":1,"#$Erfolg":1,"#Sie können Abfragen hinzufügen, um die Funktionalität dieser API-Anfrage zu erweitern. Fügen Sie im Abschnitt <span ljsid-1=\"\">„URL Parameter“</span> einen Parameter mit dem Namen „ <span ljsid-3=\"\">Anfrage</span> “ ein und geben Sie als Wert eine Abfrage im JSON-Format an.":1,"#Sieben":1,"#oder ein":1,"#Arbeitsabläufe-":1,"#„API_Version“":1,"#Mit der Job Status API können Sie den Fortschritt von Veröffentlichungs- und Rücknahmevorgängen für Einträge und Assets überwachen. Diese Funktion hilft bei der Nachverfolgung des Status von Jobs und bietet umfassende Details zur Ausführung des Jobs und den im Job vorhandenen Elementen, einschließlich verschachtelter Referenzen. Lesen Sie mehr über <a ljsid-1=\"\">Verschachtelte Referenzveröffentlichung</a> .":1,"#Massenvorgang":1,"#jeweils 10":1,"#Wenn Sie <span ljsid-1=\"\">approvals=true</span> als Abfrageparameter verwenden, werden die Einträge, die den Veröffentlichungsregeln entsprechen, zur Veröffentlichung gesendet, während die Einträge, die noch keine Genehmigung von dem ihnen zugewiesenen Genehmiger erhalten haben, nicht zur Veröffentlichung gesendet werden. Wenn Sie diesen Parameter jedoch auf <span ljsid-3=\"\">FALSCH</span> setzen und einige der in der Massenveröffentlichungsanfrage enthaltenen Einträge noch keine Genehmigung von dem ihnen zugewiesenen Genehmiger erhalten haben, werden alle ausgewählten Einträge nicht zur Veröffentlichung gesendet.":1,"#„approvals=true“":1,"#skip_workflow_stage_check=true“":1,"#als":1,"#Sie können beim Erstellen von Einträgen andere Einträge und/oder Assets in das <a ljsid-1=\"\">Rich-Text-Editor</a> (RTE)-Feld einbetten. Im RTE-Feld können Sie Einträge inline einbetten; auf Blockebene; oder als Hyperlink; und Assets als herunterladbare Einheiten oder zeigen Sie sie einfach an (für Bilder).":1,"#„Umfeld“":1,"#geplanten Aufhebung der Veröffentlichung":1,"#<span ljsid-0=\"\">Orte</span>: Übergeben Sie die Locale-Codes, in denen Sie Ihren Eintrag und seine Referenzen veröffentlichen möchten. Wenn Sie kein Quellgebietsschema angeben, werden die Einträge automatisch im Mastergebietsschema veröffentlicht.":1,"#Geplanten Veröffentlichung":1,"#Innerhalb der modularen Blöcke \"content_container\" gibt es einen Block \"link_module\". Innerhalb des link_module-Blocks gibt es modulare \"link_components\"-Blöcke. Innerhalb der modularen link_components-Blöcke gibt es einen \"link_component\"-Block. In einem solchen Szenario mit verschachtelten modularen Blöcken können einzelne Zeilenfelder mit der folgenden <span ljsid-1=\"\">Aktualisieren</span> Operation aktualisiert werden:":1,"#Weitere Informationen zu den Abfragen finden Sie im <a ljsid-1=\"\">Abschnitt „Abfragen“ des Inhaltsbereitstellungs-API-Dokuments</a> .":1,"#Sie können Abfragen hinzufügen, um die Funktionalität dieses API-Aufrufs zu erweitern. Fügen Sie im Abschnitt <span ljsid-1=\"\">„URL Parameter“</span> einen Parameter mit dem Namen „ <span ljsid-3=\"\">Anfrage</span> “ ein und geben Sie als Wert eine Abfrage im JSON-Format an.":1,"#Die Eintragsmetadaten finden Sie unter dem Schlüssel <span ljsid-1=\"\">_Metadaten</span> in der Antwort. Es wird wie folgt einer bestimmten Erweiterungs-UID zugeordnet:":1,"#REST-API":1,"#ist nicht":1,"#Ist":1,"#gleicht":1,"#enthält":1,"#endet mit":1,"#„JSON-Schema zum Erstellen eines Inhaltstyps“":1,"#FALSCH":1,"#Fügen Sie im Abschnitt „URL Parameter“ einen Parameter mit dem Namen „ <span ljsid-1=\"\">Anfrage</span> “ ein und geben Sie als Wert eine Abfrage im JSON-Format an. (Weitere Informationen zu den Abfragen finden Sie im <a ljsid-3=\"\">Abschnitt „Abfragen“ des Dokuments „Inhalt Bereitstellung API“.</a> )":1,"#„_Zweig“":1,"#wahr":1,"#Zweig-":1,"#Geben Sie beim Ausführen des API-Aufrufs im Abschnitt „URL Parameter“ die UID Ihres Alias an.":1,"#Um das Löschen eines Alias zu bestätigen, müssen Sie den Abfrageparameter <span ljsid-1=\"\">„force=true“</span> angeben.":1,"#Nur Stack-Besitzer, Administratoren und Entwickler können einem Zweig einen neuen Alias zuweisen. Sie dürfen das Authtoken nur zum Zuweisen eines Alias verwenden.":1,"#Die Anfrage gibt Informationen zu einem bestimmten Alias zurück.":1,"#Gewalt":1,"#Umfang.":1,"#, usw.):":1,"#Skript":1,"#, und":1,"#Stil":1,"#Figur":1,"#Die E-Mail Einladung enthält einen Link (z. B. <span ljsid-1=\"\">/stack/accept_ownership/{ownership_token}?api_key={api_key}&amp;uid={user_uid}</span> ), der aus dem Eigentumstoken, dem API-Schlüssel und der Benutzer-UID besteht.":1,"#Mehr erfahren über die <a ljsid-1=\"\">Erste Schritte mit der Verwendung der Postman Collection</a> for Contenstack Inhalt Management API.":1,"#Melden Sie sich bei Ihrem Konto an":1,"#Die <span ljsid-1=\"\">Get all terms across all taxoomies</span> request returns comprehensive information of all the terms across all taxonomy available in a particular stack in your organization.":1,"#Die <span ljsid-1=\"\">Get all assets</span> request returns comprehensive information on all assets available in a stack.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: To unpublish localized entries, you must include the <span ljsid-2=\"\">publish_all_localized=true</span> query parameter. This feature is plan-based and might not be enabled by default for your organization. Reach out to our <a ljsid-4=\"\">Unterstützung</a> team to enable this feature for your organization.":1,"#Die <span ljsid-1=\"\">Unpublish an entry</span> call will unpublish an entry at once, and also, gives you the provision to unpublish an entry automatically at a later date/time.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: To publish localized entries, you must include the <span ljsid-2=\"\">publish_all_localized=true</span> query parameter. This feature is plan-based and might not be enabled by default for your organization. Reach out to our <a ljsid-4=\"\">Unterstützung</a> team to enable this feature for your organization.":1,"#Die <span ljsid-1=\"\">Delete a term</span> request deletes an existing term and all the child terms within it.":1,"#Die <span ljsid-1=\"\">Publish an entry</span> request lets you publish an entry either immediately or schedule it for a later date/time.":1,"#Die <span ljsid-1=\"\">Import Entry</span> calls given below help you to import entries by uploading JSON files.":1,"#Die <span ljsid-1=\"\">Get Details of All Versions of an Entry</span> request allows you to retrieve the details of all the versions of an entry.":1,"#Die <span ljsid-1=\"\">Set Version Name for Entry</span> request allows you to assign a name to a specific version of an entry.":1,"#<strong ljsid-0=\"\">Hinweis:</strong> By default, the <span ljsid-2=\"\">force</span> query parameter is set to <span ljsid-4=\"\">false</span>, which results in an error if an attempt is made to move a term with child terms. When set to <span ljsid-6=\"\">wahr</span>, it will forcefully move the term, impacting the hierarchy of all its child terms and ancestors.":1,"#Die <span ljsid-1=\"\">SUB operation</span> works the opposite of ADD. It reads the latest value of a “Number” field and decrements it by a numeric value passed along with the operator.":1,"#Die <span ljsid-1=\"\">ADD operation </span>reads the latest value of a “Number” field and increments it by a numeric passed along with the operator. The increment occurs irrespective of what the current value of the field is.":1,"#Die <span ljsid-1=\"\">UPDATE operation</span> allows you to update data at a specific index. This operation works for both singular fields and fields marked “Multiple”.":1,"#Die<span ljsid-1=\"\">PULL operation</span>allows you to pull data from an array field based on a query passed.":1,"#Die <span ljsid-1=\"\">PUSH operation</span> allows you to “push” (or append) data into an array without overriding an existing value.":1,"#Die <span ljsid-1=\"\">Aktualisieren einen Eintrag mit JSON RTE</span> call lets you update the content of an existing entry.":1,"#Die <span ljsid-1=\"\">order</span> key signifies the term's position relative to other terms at the same level. The order of terms starts from 1, so to place a term in the first position at that level, set the order as 1.":1,"#Die <span ljsid-1=\"\">Update an entry</span> call lets you update the content of an existing entry.":1,"#Die <span ljsid-1=\"\">Create an entry with taxonomy</span> request lets you create a new entry for a selected content type that contains a taxonomy field.":1,"#Die <span ljsid-1=\"\">Create an entry with custom asset field</span> request is used to create an entry with a custom field that accepts data of type asset.":1,"#Die <span ljsid-1=\"\">Create an entry with master locale</span> request lets you create an entry in the master language of your stack if it does not already exist or has been deleted. You can use the UID of a <a ljsid-3=\"\">localized entry</a> to convert it into a <a ljsid-5=\"\">master language entry</a>.":1,"#<strong ljsid-0=\"\">Hinweis:</strong> Die <span ljsid-2=\"\">children</span> block should be added while creating an entry with a referenced entry and asset to help point the cursor after embedding an entry or asset. The schema of this block is as follows:":1,"#Die <span ljsid-1=\"\">Erstellen einen Eintrag mit JSON RTE</span> request lets you create a new entry for a selected content type that contains a JSON RTE field.":1,"#Die <span ljsid-1=\"\">Reorder a term</span> request is used to reposition an existing term available in a particular taxonomy.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: In the above code, in place of rte-field-uid, you need to provide the UID of the Rich Text Editor field.":1,"#Die <span ljsid-1=\"\">Create an entry</span> call creates a new entry for the selected content type.":1,"#Die <span ljsid-1=\"\">Get all entries</span> call fetches the list of all the entries of a particular content type. It also returns the content of each entry in JSON format. You can also specify the environment and locale of which you wish to get the entries.":1,"#Die <span ljsid-1=\"\">Import a global field</span> call imports a global field into a stack.":1,"#Die <span ljsid-1=\"\">Delete global field</span> request allows you to delete a specific global field.":1,"#Geben Sie beim Ausführen des API-Aufrufs im Abschnitt „URL Parameter“ die eindeutige ID Ihres globalen Felds an. <span ljsid-1=\"\">To configure the permissions for your application via OAuth, </span>please include the <span ljsid-3=\"\"><span ljsid-3-0=\"\">cm.global-fields.management:read</span></span> scope.":1,"#Die <span ljsid-1=\"\">Get a single global field</span> request allows you to fetch comprehensive details of a specific global field.":1,"#<strong ljsid-0=\"\">Additional Resource</strong>: You can create a dynamic and flexible Global field either by nesting <a ljsid-2=\"\">Global field within the Modular Block</a> oder <a ljsid-4=\"\">Group field within Global field</a>":1,"#Die <span ljsid-1=\"\">Get ancestors of a term</span> returns all the terms that are at higher levels in a specific taxonomy of the specified term.":1,"#Die <span ljsid-1=\"\">Get descendants of a term</span> request returns all the child terms of a specific term available in a particular taxonomy.":1,"#Die <span ljsid-1=\"\"> Compare specific global field between branches</span> request returns all the differences of the specified global field between the two specified branches.":1,"#Die <span ljsid-1=\"\">Compare specific content type between branches</span> request returns all the differences of the specified content type between the two specified branches.":1,"#Die <span ljsid-1=\"\">Compare global fields between branches</span> request returns a list of all the differences in global fields between the two specified branches.":1,"#Die <span ljsid-1=\"\">Compare content types between branches</span> request returns a list of all the differences in content types between the two specified branches.":1,"#Die <span ljsid-1=\"\">Compare branches</span> request returns a list of all the differences between two branches.":1,"#Die <span ljsid-1=\"\">Delete a branch</span> request deletes an existing branch and all the content within it.":1,"#<strong ljsid-0=\"\">Hinweis:</strong> Only stack owners, admins, and developers can create a new branch. You must only use the authtoken to create a branch.":1,"#Die <span ljsid-1=\"\">Create a branch</span> request creates a new branch in a particular stack of your organization.":1,"#Die <span ljsid-1=\"\">Get all branches</span> request returns comprehensive information of all the branches available in a particular stack in your account.":1,"#Die <span ljsid-1=\"\">Unshare a stack</span> call unshares a stack with a user and removes the user account from the list of collaborators. Once this call is executed, the user will not be able to view the stack in their account.":1,"#Die <span ljsid-1=\"\">Share a stack</span> call shares a stack with the specified user to collaborate on the stack.":1,"#The editor normally uses the \"enter\" key for paragraphs and \"shift+enter\" for line breaks. However, by enabling <span ljsid-1=\"\">\"cs_only_breakline\": true</span> und <span ljsid-3=\"\">\"cs_breakline_on_enter\": true</span> im <span ljsid-5=\"\">\"rte\"</span> parameter, pressing \"enter\" creates a line break, and \"shift+enter\" creates a new paragraph.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: Wir unterstützen derzeit vier Attribute (<span ljsid-2=\"\">GD:Schriftgröße</span>, <span ljsid-4=\"\">GD:Farbe</span>, <span ljsid-6=\"\">GD:Hintergrundfarbe</span>, und <span ljsid-8=\"\">MW:Farbe</span>) for this key. This is applicable for both HTML and JSON Rich Text Editors. For more information, refer to the <a ljsid-10=\"\">API- Ändern</a> für dieses Update.":1,"#<span ljsid-0=\"\">„sys_rte_skip_format_on_paste“: „GD: Hintergrundfarbe“</span>: Überspringt das <span ljsid-2=\"\">Hintergrundfarbe</span> Attribut und GD gibt das Präfix des externen Anbieters Google Document an.":1,"#<span ljsid-0=\"\">„sys_rte_skip_format_on_paste“: „GD:color“</span>: Überspringt das <span ljsid-2=\"\">Farbe</span> Attribut und GD gibt das Präfix des externen Anbieters Google Document an.":1,"#<span ljsid-0=\"\">\"sys_rte_skip_format_on_paste\": \"GD:font-size\"</span>: Überspringt das <span ljsid-2=\"\">font-size</span> Attribut und GD gibt das Präfix des externen Anbieters Google Document an.":1,"#Ein <strong ljsid-1=\"\">Authtoken</strong> is a read-write token used to make authorized CMA requests, and it is a <strong ljsid-3=\"\">user-specific</strong> token. This means that your personal user details are attached to every API request that you make using the authtoken. So, if a person were to obtain access to your authtoken, and knows the Stack API key, this person would be able to make API requests that appeared to be coming from you.":1,"#Die <span ljsid-1=\"\">Add stack settings</span> request lets you add additional settings for your existing stack.":1,"#Die <span ljsid-1=\"\">Get stack settings</span> call retrieves the configuration settings of an existing stack.":1,"#Die <span ljsid-1=\"\">Accept stack owned by other user</span> call allows a user to accept the ownership of a particular stack via an email invitation.":1,"#Die <span ljsid-1=\"\">Transfer stack ownership to other users</span> call sends the specified user an email invitation for accepting the ownership of a particular stack.":1,"#Die <span ljsid-1=\"\">Update User Role</span> API Request updates the roles of an existing user account. This API Request will override the existing roles assigned to a user. For example, we have an existing user with the \"Developer\" role, and if you execute this API request with \"Content Manager\" role, the user role will lose \"Developer\" rights and the user role be updated to just \"Content Manager\".":1,"#Die <span ljsid-1=\"\">Get all users of a stack</span> call fetches the list of all users of a particular stack":1,"#Die <span ljsid-1=\"\">Delete stack</span> call is used to delete an existing stack permanently from your Contentstack account.":1,"#Die <span ljsid-1=\"\">Update stack</span> call lets you update the name and description of an existing stack.":1,"#Die <span ljsid-1=\"\">Create stack</span> call creates a new stack in your Contentstack account.":1,"#Pass the stack’s API key against the <span ljsid-1=\"\">API-Schlüssel</span> parameter as header for stack based APIs":1,"#Die <span ljsid-1=\"\">Get all stacks</span> call fetches the list of all stacks owned by and shared with a particular user account.":1,"#Die <span ljsid-1=\"\">Remove a stack role mapping</span> request allows you to delete the associations of team users for a specified stack in your organization.":1,"#Die <span ljsid-1=\"\">Update a stack role mapping</span> request allows you to update the stack roles for a specific stack in your organization. You need to pass the role UIDs in the request body as follows:":1,"#Die <span ljsid-1=\"\">Add a stack role mapping</span> request allows you to associate users from a specified team with the available stacks in your organization.":1,"#Die <span ljsid-1=\"\">Get all stack role mapping</span> request allows you to retrieve details of all associated stacks for a specified team in your organization.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: Only the Owner or the Admin of the organization can remove users from a team.":1,"#Die <span ljsid-1=\"\">Remove a user from team</span> request allows you to remove an existing user from a particular team.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: Only the Owner or the Admin of the organization can add users to a team.":1,"#Die <span ljsid-1=\"\">Add users to team</span> request allows you to send invitations to add users and assign them organizational and stack roles.":1,"#Die <span ljsid-1=\"\">Get all users of team</span> request retrieves information about all the users associated with a particular team.":1,"#All accounts registered with Contentstack are known as <a ljsid-1=\"\">Benutzer</a>. An organization can have many users with varying permissions and roles.":1,"#Die <span ljsid-1=\"\">Delete a team</span> request deletes an existing team along with all its associated users and assigned roles.":1,"#Die <span ljsid-1=\"\">Update a team</span> request is used to modify details, such as adding or removing users from a team, assigning or removing stack roles within a team, updating team descriptions, and updating organization roles for an existing team within a specific organization.":1,"#Die <span ljsid-1=\"\">Create a team</span> request creates a team in the specified organization.":1,"#Die <span ljsid-1=\"\">Get a single team</span> request returns comprehensive information of a specific team available in a particular organization.":1,"#Die <span ljsid-1=\"\">Get all teams</span> request returns comprehensive information of all the teams available in your organization.":1,"#Die <span ljsid-1=\"\">Get organization log item</span> request is used to retrieve a specific item from the audit log of an organization.":1,"#Die <span ljsid-1=\"\">Get organization log details</span> request is used to retrieve the audit log details of an organization.":1,"#Die <span ljsid-1=\"\">Get all stacks in an organization</span> call fetches the list of all stacks in an Organization.":1,"#Die <span ljsid-1=\"\">Transfer organization ownership</span> call transfers the ownership of an Organization to another user. When the call is executed, an email invitation for accepting the ownership of a particular Organization is sent to the specified user.":1,"#Die <span ljsid-1=\"\">Get all organization invitations</span> call gives you a list of all the Organization invitations. Only the owner or the admin of the Organization can resend the invitation to add users to an Organization.":1,"#Die <span ljsid-1=\"\">Resend pending organization invitation</span> request allows you to resend the Organization invitations to users who have not yet accepted the earlier invitation. Only the owner or the admin of the Organization can resend the invitation to add users to an Organization.":1,"#Die <span ljsid-1=\"\">Remove users from organization</span> request allows you to remove existing users from your organization.":1,"#When executing the API request, in the request body, provide the organization admin/member role ID, obtained from the <span ljsid-1=\"\">Get all roles in an Organization</span> request. Also, provide the stack role UID of the user in the request body, obtained from the <span ljsid-3=\"\">Get all roles</span> Anfrage.":1,"#Die <span ljsid-1=\"\">Add users to organization</span> request allows you to send invitations to add users to your organization. Only the owner or the admin of the organization can add users.":1,"#Die <span ljsid-1=\"\">Get Organization users by email</span> request retrieves information about users within an organization based on their email addresses.":1,"#Contentstack provides <strong ljsid-1=\"\">token-based authentication</strong> that allows you to create, update, delete, and fetch the content of your Contentstack account. You can use either the stack’s Management Token, OAuth Token, or the user Authtoken, along with the stack API key, to make Content Management API requests. The API key is a unique key assigned to each <a ljsid-3=\"\">Stapel</a>.":1,"#Die <span ljsid-1=\"\">Get all roles in an organization</span> call gives the details of all the roles that are set to users in an Organization.":1,"#Die <span ljsid-1=\"\">Get a single organization</span> call gets the comprehensive details of a specific organization related to the system user.":1,"#Die <span ljsid-1=\"\">Get all organizations</span> call lists all organizations related to the system user in the order that they were created.":1,"#Die <span ljsid-1=\"\">Reset password</span> API request allows you to reset your Contentstack account password.":1,"#Die <span ljsid-1=\"\">Request for a password</span> API helps to get a temporary password to log into an account in case a user has forgotten the login password.":1,"#Die <span ljsid-1=\"\">Activate a user account</span> call activates the account of a user after signing up. For account activation, you will require the token received in the activation email.":1,"#Die <span ljsid-1=\"\">Update User</span> API Request updates the details of an existing user account. Only the information entered here will be updated, the existing data will remain unaffected.":1,"#Die <span ljsid-1=\"\">Get user</span> call returns comprehensive information of an existing user account. The information returned includes details of the stacks owned by and shared with the specified user account.":1,"#Die <span ljsid-1=\"\">Log out of your account</span> call is used to sign out the user of Contentstack account.":1,"#<strong ljsid-0=\"\">Hinweis:</strong> Die <span ljsid-2=\"\">Authtoken</span> is a mandatory parameter when executing Content Management API calls. However, when executing Content Delivery API calls, use <a ljsid-4=\"\">the Content Delivery base URL </a>for your region, and pass the environment-specific delivery token against the <span ljsid-6=\"\">Zugangstoken</span> Schlüssel.":1,"#Die <span ljsid-1=\"\">Log in to your account</span> request is used to sign in to your Contentstack account and obtain the authtoken.":1,"#<strong ljsid-0=\"\">*</strong> Contentstack returns the <strong ljsid-2=\"\">422</strong> HTTP status code with the \"UID is not valid\" message when an entry doesn’t exist, has been deleted, or belongs to a different content type. To check if an entry has been deleted, first try retrieving it from the CDN, then from the origin server if needed. This error can also occur due to invalid query parameters, such as using an empty array with logical operators like <span ljsid-4=\"\">$und</span>. Always ensure your queries contain valid conditions. For example, <span ljsid-6=\"\">{\"$and\": [{}, {}]}</span> is not a valid query.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: Only the organization Owner and Admin users can create OAuth Tokens.":1,"#Navigate to <strong ljsid-1=\"\">Einstellungen</strong> &gt; <strong ljsid-3=\"\">Tokens</strong> &gt; <strong ljsid-5=\"\">Management-Token</strong>.":1,"#<strong ljsid-0=\"\">Tip</strong>: An alternate way to retrieve the authtoken is via <strong ljsid-2=\"\">Inspect</strong> element. If you are logged in through your browser, right-click and select <strong ljsid-4=\"\">Inspect</strong> or press “F12” to open developer tools, and select the <strong ljsid-6=\"\">Network</strong> Tab.":1,"#Die <span ljsid-1=\"\">Update a term</span> request is used to update the details of an existing term available in a particular taxonomy.":1,"#Since terms are organized hierarchically in a taxonomy, it's important to define the order when creating new terms. For instance, when creating a term at the parent level, set the <span ljsid-1=\"\">parent_uid</span> as <span ljsid-3=\"\">Null</span> and specify the level within the order parameter. To create a child term, provide the <span ljsid-5=\"\">parent_uid</span> of the parent term where you want to add the new child term, and indicate the desired level within the order parameter.":1,"#Die <span ljsid-1=\"\">Create a term</span> request creates a term in a particular taxonomy within your stack.":1,"#Die <span ljsid-1=\"\">Get a single term</span> request returns comprehensive information of a specific term available in a particular taxonomy.":1,"#Die <span ljsid-1=\"\">Get all terms of a taxonomy</span> request returns comprehensive information of all the terms within a taxonomy available in a particular stack in your organization.":1,"#Die <span ljsid-1=\"\">Delete a taxonomy</span> request deletes an existing taxonomy and all the terms within it. To confirm the deletion of a taxonomy, you need to specify the <span ljsid-3=\"\">force=true</span> query parameter.":1,"#<strong ljsid-0=\"\">Hinweis</strong>: If the CSV import format is invalid, any invalid rows containing taxonomy/terms and subsequent rows will be ignored. Only rows with valid taxonomy/terms will be created. Refer to our <a ljsid-2=\"\">Import a Taxonomy</a> document for more information.":1,"#Die <span ljsid-1=\"\">Import a taxonomy</span> request is used to import a taxonomy and its terms into a stack by uploading the JSON or CSV file.":1,"#Die <span ljsid-1=\"\">Export a taxonomy</span> request is used to export a specific taxonomy and its terms. The file is exported in JSON or CSV format. The exported file won’t get downloaded automatically. To download the exported file, a REST API client, such as Postman can be used.":1,"#Die <span ljsid-1=\"\">Update a taxonomy</span> request is used to update the details of an existing taxonomy available in a particular stack.":1,"#Die <span ljsid-1=\"\">Create a taxonomy</span> request creates a taxonomy in a particular stack of your organization.":1,"#Die <span ljsid-1=\"\">Get a single taxonomy</span> request returns comprehensive information of a specific taxonomy available in a particular stack.":1,"#Die <span ljsid-1=\"\">Get all taxonomies</span> request returns comprehensive information of all the taxonomies available in a particular stack in your organization.":1,"#Navigate to <strong ljsid-1=\"\">Einstellungen</strong> &gt; <strong ljsid-3=\"\">Stapel</strong>.":1,"#Die <span ljsid-1=\"\">Delete Content Type</span> call deletes an existing content type and all the entries within it.":1,"#Die <span ljsid-1=\"\">Update Content Type</span> call is used to update the schema of an existing content type.":1,"#Die <span ljsid-1=\"\">Create content type with taxonomy</span> request shows you how to add a taxonomy field while creating a content type.":1,"#Die <span ljsid-1=\"\">Create content type with custom asset field</span> request is used to create a content type with a custom field that accepts data of type asset.":1,"#Under the <span ljsid-1=\"\">Bezug auf</span> parameter, mention the UIDs of the content types whose entries you wish to embed within the JSON RTE field.":1,"#To add key-value pairs as choices, under <span ljsid-1=\"\">Aufzählung</span>, set the <span ljsid-3=\"\">fortschrittlich</span> parameter to <span ljsid-5=\"\">wahr</span> and define the key-value choices under the <span ljsid-7=\"\">choices</span> parameter.":1,"#To mark a field as non-unique, you need to set the <span ljsid-1=\"\">einzigartig</span> parameter to <span ljsid-3=\"\">false</span>. For example, to remove the <span ljsid-5=\"\">einzigartig</span> constraint on the default 'title' field, you need to update the JSON schema of the title field as follows:":1,"#Die <span ljsid-1=\"\">Get a single content type</span> call returns information of a specific content type.":1,"#Die <span ljsid-1=\"\">Delete an alias</span> request deletes an existing alias.":1,"#Die <span ljsid-1=\"\">Assign an alias</span> request creates a new alias in a particular stack of your organization. This alias can point to any existing branch (target branch) of your stack.":1,"#Ein <a ljsid-1=\"\">alias</a> acts as a pointer to a particular branch. You can specify the alias ID in your frontend code to pull content from the target branch associated with an alias.":1,"#Die <span ljsid-1=\"\">Get single merge job</span> request returns the status and configuration details of a particular merge job.":1,"#Die <span ljsid-1=\"\">Get all merge jobs</span> request returns a list of all the recent merge jobs within a specific period.":1,"#Die <span ljsid-1=\"\">Merge branches</span> request merges the specified two branches as per the merge strategy selected.":1,"#Die <a ljsid-1=\"\">Merging Branches </a>functionality enables you to merge two branches, integrating the development changes made in the compare branch into the base branch.":1,"#<strong ljsid-0=\"\">Contentstack OAuth</strong> employs the OAuth 2.0 protocol, enabling external applications to access Contentstack APIs on behalf of users. It issues access tokens (App &amp; User tokens) to client applications, allowing them to retrieve restricted data from the Contentstack resource server without the need for the resource owner to share their credentials. Learn more about <a ljsid-2=\"\">Contentstack OAuth</a> und <a ljsid-4=\"\">OAuth-Bereiche</a>.":1,"#Die <strong ljsid-1=\"\">Content-Management-API (CMA)</strong> is used to manage the content of your Contentstack account. This includes creating, updating, deleting, and fetching content of your account. To use the Content Management API, you will need to authenticate yourself with a <a ljsid-3=\"\">Management-Token</a> or an <a ljsid-5=\"\">Authtoken</a>. Read more about it in <a ljsid-7=\"\">Authentifizierung</a>.":1,"#Auden Hinton, Director of Digital Experience bei Ellie Mae":1,"#Clay Gregory":1,"#Clay Gregoryy":1,"#2-mal schnellerer":1,"#Schnelle und kostengünstige":1,"#Webinar-":1,"#führenden Headless CMS":1,"#unseren Kunden (und unseren zukünftigen Kunden) am besten dabei helfen":1,"#„Wie man eine zusammensetzbare Plattform auswählt“":1,"#Vous pouvez passer le <span ljsid-1=\"\">sys_rte_skip_format_on_paste</span> clé dans le <span ljsid-3=\"\">stack_variables</span> section dans le corps de la demande comme suit:":1,"#Stimuler la croissance: Stratégies pour une data driven operating model":1,"#I love how we don’t have to involve development to tweak text or a":1,"#/de/docs/changelog":1,"#Live Edit Tags for Entries (facultatif)":1,"#A Contentstack and Edba Academy initiative to equip women college graduates with industry-ready skills relevant to the tech industry.":1,"#<em ljsid-0=\"\">Contentstack hat Recht. Diese Funktionalität muss in einer einzigen Schnittstelle zusammengeführt werden, um personalisierte Erlebnisse zu schaffen.“</em> <span ljsid-2=\"\">Stirbt</span> bezieht sich darauf, wie Marketingfachleute mithilfe generativer KI unsere Arbeitsweise ändern können, ohne die menschliche/markenbezogene Stimme zu verlieren.":1,"#Zeichen":1,"#Warum ein Composable CMS das Richtige für Sie ist":1,"#If you want to understand how building scale brings a welcome change to your business, use Contentstack. To know more, <a ljsid-1=\"\">Rede mit uns</a>.":1,"#As you scale, maintain quality <a ljsid-1=\"\">Kundenerfahrungen</a> for long-term success. Invest in customer service and support systems that grow alongside your business. Satisfied customers become your loyal advocates, ensuring sustained growth through word-of-mouth marketing.":1,"#<a ljsid-0=\"\">Ebner Media</a> wanted to change from print to digital magazines and move from WordPress to a more flexible CMS. They chose <a ljsid-2=\"\">Das kopflose CMS von Contentstack</a> to reduce development time and resources, allowing for rapid product launches. The new system allowed Ebner Media to digitize its print publications, enabling localization and the creation of a revenue stream through licensing. Ebner Media utilizes AI for various tasks, improving efficiency and global reach. Key benefits include unlimited scalability, a modern technology stack and expansion into new markets with localized content.":1,"#Discover the importance of scaling your business. When you use automation tools and data-driven insights, you optimize resource allocation and enhance customer satisfaction. To enhance your scalability and create a more robust and efficient business, <a ljsid-1=\"\">Rede mit uns</a> Heute.":1,"#<span ljsid-0=\"\">Showing <strong ljsid-0-1=\"\">27</strong></span> results for <strong ljsid-3=\"\">postman</strong>":1,"#Using Repeat Paths to Automate Repetitive Tasks This use case covers a scenario where you can dynamically create multiple entries in Contentstack using the Repeat Path feature. In this use case, we send bulk data via Postman and fetch the data in the HTTP trigger. Once the data is fetched, you need to configure the Repeat Path. Select the HTTP trigger data via the Data source field in the Repeat Path configuration. Note: You can use any trigger or action to fetch the data from any source. Configure the Contentstack action and select the Create an Entry action inside the repeat path. In the Cre":1,"#/docs/developers/automation-hub-guides/using-repeat-paths-to-automate-repetitive-tasks":1,"#<em ljsid-0=\"\">Postman</em> Collections | Documentation":1,"#<strong ljsid-0=\"\">Leader in content experience platforms. </strong>Die <em ljsid-2=\"\"><strong ljsid-2-0=\"\">Aragon Research Globe™ award</strong></em> recognizes how Contentstack’s low-code, easy content creation and publishing and advanced front-end hosting redefine customer experiences. <a ljsid-4=\"\"><strong ljsid-4-0=\"\">Join our group demo</strong></a> to experience this dynamic solution.":1,"#Discover the importance of scaling your business. When you use automation tools and data-driven insights, you optimize resource allocation and enhance customer satisfaction. To enhance your scalability and create a more robust and efficient business, <a ljsid-1=\"\">talk to us</a> Heute.":1,"#Ebner Media":1,"#Today’s cons":1,"#than its dynamic, CMS-based counterpart? Dynamic sites go back to the server to render each page every single time someone visits it while static site generators store a “pre-built” version that can be delivered nearly instantly.":1,"#10 times faster":1,"#So what makes many a static site as much as":1,"#of scaling, chances are it’s the latter.":1,"#hopes":1,"#Unless you somehow saw this one coming or have been overpaying in":1,"#modernized the concept and brought it back into the spotlight as a lightweight alternative to traditional, database-driven, dynamic websites—but that doesn’t mean it’s just some fad.":1},"version":59144}]