\n \n {fieldName.replace(/([A-Z])/g, ' $1').trim()}\n {isRequired && *}\n \n {inputElement}\n {fieldConfig.format && (\n

Format: {fieldConfig.format}

\n )}\n

\n );\n };\n\n return (\n

\n {isImport ? 'Import New Account' : `Edit Account ${account?.UID}`}\n

\n\n

\n {/* UID field for import */}\n {isImport && (\n

Account Identifier

\n \n UID (optional - will be generated if not provided)\n \n \n

\n )}\n\n {/* Profile Fields */}\n {schema?.profileSchema?.fields && (\n

Profile Information

\n {Object.entries(schema.profileSchema.fields).map(([fieldName, fieldConfig]) =>\n renderField(fieldName, fieldConfig, 'profile', account?.profile?.[fieldName])\n )}\n

\n )}\n\n {/* Common Profile Fields (if no schema) */}\n {!schema?.profileSchema?.fields && (\n

Profile Information

\n \n First Name\n \n \n

\n \n Last Name\n \n \n

\n \n Email\n \n \n

\n )}\n\n {/* Data Fields */}\n {schema?.dataSchema?.fields && (\n

Custom Data

\n {Object.entries(schema.dataSchema.fields).map(([fieldName, fieldConfig]) =>\n renderField(fieldName, fieldConfig, 'data', account?.data?.[fieldName])\n )}\n

\n )}\n\n {/* Custom Data Fields (if account has data but no schema) */}\n {!schema?.dataSchema?.fields && account?.data && Object.keys(account.data).length > 0 && (\n

Custom Data

\n {Object.entries(account.data).map(([fieldName, value]) => (\n

\n \n {fieldName}\n \n \n

\n ))}\n

\n )}\n\n {/* Add Custom Data Field */}\n

Add Custom Data Field

\n \n Field Name\n \n \n

\n \n Field Value (JSON format)\n \n \n

\n \n Add Field\n \n

\n\n {/* Form Actions */}\n

\n \n Cancel\n \n \n {isImport ? 'Import Account' : 'Update Account'}\n \n

\n\n {/* JavaScript for dynamic field addition and form submission */}\n \n \n \n \n \n

{children}

\n \n \n );\n}",[],[162,180,211],[162,180],{"_104":219,"_97":220,"_163":221,"_165":164,"_166":145,"_167":168,"_169":118,"_106":222,"_101":33,"_171":223,"_173":224,"_174":22,"_175":-5,"_176":225,"_100":226},"c4ca1198-1299-11f1-935e-42dde27851f2","index.tsx","019c96ee-0298-70c4-b317-5b6ab0bbace3",["D",1772058706545],"http","/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\nimport { Hono } from \"https://esm.sh/hono@4.0.0\";\nimport { readFile, serveFile } from \"https://esm.town/v/std/utils@85-main/index.ts\";\nimport { AccountForm } from \"./components/AccountForm.tsx\";\nimport { AccountSearch } from \"./components/AccountSearch.tsx\";\nimport { AccountViewer } from \"./components/AccountViewer.tsx\";\nimport { Layout } from \"./components/Layout.tsx\";\n\nconst app = new Hono();\n\n// Unwrap Hono errors to see original error details\napp.onError((err, c) => {\n throw err;\n});\n\n// Gigya API Configuration\nconst GIGYA_DOMAIN = Deno.env.get(\"GIGYA_DOMAIN\") || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = Deno.env.get(\"GIGYA_API_KEY\") || \"\";\nconst GIGYA_APP_KEY = Deno.env.get(\"GIGYA_APP_KEY\") || \"\";\nconst GIGYA_APP_SECRET = Deno.env.get(\"GIGYA_APP_SECRET\") || \"\";\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.warn(\"Missing Gigya environment variables. Some features may not work.\");\n}\n\n// Direct Gigya API functions\nasync function makeGigyaRequest(endpoint: string, params: Record): Promise {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`HTTP ${response.status}: ${text}`);\n }\n\n const result = await response.json();\n\n if (result.errorCode !== 0) {\n throw new Error(`Gigya API Error ${result.errorCode}: ${result.errorMessage || \"Unknown error\"}`);\n }\n\n return result;\n}\n\nasync function getAccountInfo(uid: string, include?: string) {\n try {\n const response = await makeGigyaRequest(\"accounts.getAccountInfo\", {\n UID: uid,\n include: include\n || \"profile,data,communications,groups,loginIDs,lastLogin,lastLoginLocation,registrationTimestamp,verified,verifiedTimestamp,oldestDataUpdated,oldestDataUpdatedTimestamp\",\n });\n return response;\n } catch (error) {\n console.error(`Error fetching account info for UID ${uid}:`, error);\n return null;\n }\n}\n\nasync function setAccountInfo(uid: string, accountData: {\n profile?: any;\n data?: any;\n communications?: any;\n}) {\n try {\n const params: Record = { UID: uid };\n\n if (accountData.profile) {\n params.profile = JSON.stringify(accountData.profile);\n }\n\n if (accountData.data) {\n params.data = JSON.stringify(accountData.data);\n }\n\n if (accountData.communications) {\n params.communications = JSON.stringify(accountData.communications);\n }\n\n const response = await makeGigyaRequest(\"accounts.setAccountInfo\", params);\n return response;\n } catch (error) {\n console.error(`Error updating account ${uid}:`, error);\n throw error;\n }\n}\n\nasync function importAccount(accountData: {\n profile?: any;\n loginIDs?: any;\n password?: any;\n data?: any;\n UID?: string;\n}) {\n try {\n const params: Record = {};\n\n if (accountData.profile) {\n params.profile = JSON.stringify(accountData.profile);\n }\n\n if (accountData.loginIDs) {\n params.loginIDs = JSON.stringify(accountData.loginIDs);\n }\n\n if (accountData.password) {\n params.password = JSON.stringify(accountData.password);\n }\n\n if (accountData.data) {\n params.data = JSON.stringify(accountData.data);\n }\n\n if (accountData.UID) {\n params.UID = accountData.UID;\n }\n\n const response = await makeGigyaRequest(\"accounts.importFullAccount\", params);\n return response;\n } catch (error) {\n console.error(\"Error importing account:\", error);\n throw error;\n }\n}\n\nasync function getSchema() {\n try {\n const response = await makeGigyaRequest(\"accounts.getSchema\", {});\n return response;\n } catch (error) {\n console.error(\"Error fetching account schema:\", error);\n return null;\n }\n}\n\nasync function setSchema(schemaData: {\n profileSchema?: any;\n dataSchema?: any;\n}) {\n try {\n const params: Record = {};\n\n if (schemaData.profileSchema) {\n params.profileSchema = JSON.stringify(schemaData.profileSchema);\n }\n\n if (schemaData.dataSchema) {\n params.dataSchema = JSON.stringify(schemaData.dataSchema);\n }\n\n await makeGigyaRequest(\"accounts.setSchema\", params);\n } catch (error) {\n console.error(\"Error setting account schema:\", error);\n throw error;\n }\n}\n\n// Serve static files\napp.get(\"/frontend/*\", c => serveFile(c.req.path, import.meta.url));\napp.get(\"/shared/*\", c => serveFile(c.req.path, import.meta.url));\n\n// Main page - Account search and viewer\napp.get(\"/\", async (c) => {\n try {\n const uid = c.req.query(\"uid\");\n const select = c.req.query(\"select\") || \"*\";\n const filter = c.req.query(\"filter\");\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n // Get account schema\n const schema = await getSchema();\n const searchQuery = filter ? `WHERE ${filter}` : \"\";\n const selectQuery = select ? select : \"*\";\n const query = `select ${selectQuery} from accounts ${searchQuery} limit ${Math.min(limit, 100)}`;\n console.log(\n \"Searching with query:\",\n `select ${selectQuery} from accounts ${searchQuery} limit ${Math.min(limit, 100)}`,\n );\n\n const { results: accounts, totalCount } = await makeGigyaRequest(\"accounts.search\", {\n query: query,\n openCursor: true,\n });\n\n return c.html(\n \n

Account Viewer

\n \n Import Account\n \n

\n\n \n\n {/* Search Results */}\n {accounts.length > 0 && (\n

\n Search Results ({totalCount} {totalCount === 1 ? \"account\" : \"accounts\"} found)\n

\n {totalCount > limit && (\n

\n Showing {Math.min(limit, accounts.length)} of {totalCount} results\n

\n )}\n

\n\n {accounts.map((account, index) => (\n \n ))}\n\n {/* Pagination */}\n {totalCount > limit && (\n

\n Page {page} of {Math.ceil(totalCount / limit)}\n

\n {page > 1 && (\n \n Previous\n \n )}\n {page < Math.ceil(totalCount / limit) && (\n \n Next\n \n )}\n

\n )}\n

\n )}\n\n {/* No results message */}\n {(uid || query || filter) && accounts.length === 0 && (\n

\n \n

No accounts found

\n No accounts match your search criteria. Try adjusting your search terms or using different criteria.\n

\n \n Clear Search\n \n

\n )}\n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Edit account form\napp.get(\"/edit/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n\n const [schema, account] = await Promise.all([\n getSchema(),\n getAccountInfo(uid),\n ]);\n\n if (!account) {\n return c.html(\n \n

\n Account not found\n

\n ,\n );\n }\n\n return c.html(\n \n

\n ← Back\n

Edit Account

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Import account form\napp.get(\"/import\", async (c) => {\n try {\n const schema = await getSchema();\n\n return c.html(\n \n

\n ← Back\n

Import New Account

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// API Routes\n\n// Get account info\napp.get(\"/api/account/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n const account = await getAccountInfo(uid);\n\n if (!account) {\n return c.json({ success: false, error: \"Account not found\" }, 404);\n }\n\n return c.json({ success: true, data: account });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Search accounts\napp.get(\"/api/search\", async (c) => {\n try {\n const query = c.req.query(\"q\") || \"\";\n const filter = c.req.query(\"filter\") || \"\";\n const select = c.req.query(\"select\") || \"\";\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n const result = await searchAccountsWithFilter(query, filter, select, page, limit);\n\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update account\napp.put(\"/api/account/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n const body = await c.req.json();\n\n const result = await setAccountInfo(uid, body);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Import account\napp.post(\"/api/account/import\", async (c) => {\n try {\n const body = await c.req.json();\n const result = await importAccount(body);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get schema\napp.get(\"/api/schema\", async (c) => {\n try {\n const schema = await getSchema();\n return c.json({ success: true, data: schema });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update schema\napp.put(\"/api/schema\", async (c) => {\n try {\n const body = await c.req.json();\n await setSchema(body);\n return c.json({ success: true });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Health check\napp.get(\"/api/health\", (c) => {\n return c.json({\n success: true,\n timestamp: new Date().toISOString(),\n service: \"Gigya Account Viewer\",\n });\n});\n\nexport default app.fetch;",[],[162,220],[162],{"_104":229,"_97":230,"_163":231,"_165":-5,"_166":145,"_167":232,"_169":118,"_106":233,"_101":168,"_171":172,"_173":-5,"_174":22,"_175":-5,"_176":234,"_100":263},"08b593dc-129a-11f1-8bc0-42dde27851f2","docs","06bb7484-129a-11f1-b0c0-42dde27851f2",15,["D",1772058820543],[235,245,254],{"_104":236,"_97":237,"_163":238,"_165":231,"_166":145,"_167":239,"_169":118,"_106":240,"_101":168,"_171":241,"_173":242,"_174":22,"_175":-5,"_176":243,"_100":244},"10311e24-129a-11f1-b3d7-42dde27851f2","accounts.yaml","019c96ee-0299-75ff-a0e5-202da08fb451",17,["D",1772058833096],"file","openapi: 3.0.3\ninfo:\n title: SAP Customer Data Cloud - Account API\n version: 1.0.0\n description: OpenAPI spec for Account Info, Account Update, Account Import, Schema\n configuration, and Account Search\nservers:\n- url: https://cdcs-api.example.com\npaths:\n /accounts.getAccountInfo:\n get:\n summary: Get Account Info\n parameters:\n - in: query\n name: UID\n schema:\n type: string\n required: true\n description: Unique user ID\n responses:\n '200':\n description: Account object\n content:\n application/json:\n schema:\n $ref: '#/components/schemas/Account'\n /accounts.setAccountInfo:\n post:\n summary: Update Account Info\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n profile:\n type: string\n communications:\n type: string\n data:\n type: string\n example:\n profile: '{\"firstName\":\"John\",\"lastName\":\"Doe\"}'\n communications: '{\"Marketing_Email\":{\"status\":\"optIn\"}}'\n data: '{\"customField\":\"value\"}'\n responses:\n '200':\n description: Update successful\n '400':\n description: Invalid input\n /accounts.importFullAccount:\n post:\n summary: Import a user account\n description: Imports a new user account with provided profile, login IDs, and\n password hash\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n profile:\n type: string\n loginIDs:\n type: string\n password:\n type: string\n UID:\n type: string\n example:\n profile: '{\"firstName\":\"Alice\",\"lastName\":\"Smith\"}'\n loginIDs: '{\"email\":\"alice@example.com\"}'\n password: '{\"hash\":\"abc123\",\"hashSettings\":{\"algorithm\":\"sha256\"}}'\n UID: user-001\n responses:\n '200':\n description: Account imported successfully\n '400':\n description: Invalid input\n /accounts.getSchema:\n get:\n summary: Retrieve schema configuration\n responses:\n '200':\n description: Schema definition\n content:\n application/json:\n schema:\n $ref: '#/components/schemas/Schema'\n /accounts.setSchema:\n post:\n summary: Update schema definition\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n schema:\n type: string\n example:\n schema: '{\"fields\":{\"firstName\":{\"type\":\"string\",\"required\":true}}}'\n responses:\n '200':\n description: Schema updated\n /accounts.search:\n get:\n summary: Search Accounts\n description: Search for accounts using parameters such as email or UID.\n parameters:\n - in: query\n name: email\n schema:\n type: string\n format: email\n required: false\n description: Email address to search for\n - in: query\n name: UID\n schema:\n type: string\n required: false\n description: Specific UID to search\n - in: query\n name: query\n schema:\n type: string\n required: false\n description: Free-form query string\n responses:\n '200':\n description: List of matching accounts\n content:\n application/json:\n schema:\n type: array\n items:\n $ref: '#/components/schemas/Account'\n '400':\n description: Invalid query parameters\ncomponents:\n schemas:\n Account:\n type: object\n properties:\n UID:\n type: string\n isActive:\n type: boolean\n profile:\n $ref: '#/components/schemas/Profile'\n communications:\n $ref: '#/components/schemas/Communications'\n groups:\n type: array\n items:\n type: object\n properties:\n orgId:\n type: string\n roles:\n type: array\n items:\n type: string\n status:\n type: string\n Profile:\n type: object\n properties:\n firstName:\n type: string\n lastName:\n type: string\n email:\n type: string\n format: email\n Communications:\n type: object\n additionalProperties:\n type: object\n properties:\n status:\n type: string\n optIn:\n type: object\n additionalProperties:\n type: string\n Schema:\n type: object\n properties:\n fields:\n type: object\n additionalProperties:\n type: object\n properties:\n type:\n type: string\n required:\n type: boolean\n writeAccess:\n type: string\n allowNull:\n type: boolean\n format:\n type: string\n encrypt:\n type: string",[],[230,237],{"_104":246,"_97":247,"_163":248,"_165":231,"_166":145,"_167":249,"_169":118,"_106":250,"_101":168,"_171":241,"_173":251,"_174":22,"_175":-5,"_176":252,"_100":253},"0cbb6c68-129a-11f1-8bc0-42dde27851f2","ds.md","019c96ee-0299-75ff-a0e5-3df48d3804b9",16,["D",1772058827289],"# SAP Customer Data Cloud\n\nGenerated on: 2025-06-09 18:21:06 GMT+\n\nSAP Customer Data Cloud | SHIP\n\nPublic\n\nOriginal content: https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD/8b8d6fffe113457094a17701f63e3d6a?locale=en-\n\nUS&state=PRODUCTION&version=SHIP\n\n### Warning\n\nThis document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.\n\nThe information included in custom documentation may not reect the arrangement of topics in SAP Help Portal, and may be\n\nmissing important aspects and/or correlations to other topics. For this reason, it is not for production use.\n\nFor more information, please visit https://help.sap.com/docs/disclaimer.\n\n\n## Data Store REST\n\nSAP Customer Data Cloud's Data Store (DS) API consists of the methods listed below.\n\n```\nds.delete REST\n```\n```\nds.deleteSchemaFields REST\n```\n```\nds.get REST\n```\n```\nds.getSchema REST\nds.getTypes REST\n```\n```\nds.search REST\n```\n```\nds.setSchema REST\nds.store REST\n```\n## ds.delete REST\n\n## Description\n\nDeletes object data or an entire object from Gigya's Data Store.\n\n## Request URL\n\n#### https://ds./ds.delete\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your SAP\nCustomer Data Cloud Customer Engagement Executive or email support@gigya-inc.com.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\noid string The ID of the object to delete.\n```\n```\ntype string A string indicating the type of the\nobject.\n```\n```\nelds string A comma separated list of elds\nto delete. Acceptable values for\nthis parameter:\n```\n```\nData eld names,\nspecifying the the\ncomplete path, i.e.\nalbum.photo.photoTitle_t\n```\n```\nPartial eld names (elds\nthat contain only a part\nof the path to sub-\nobjects, i.e. album.photo)\n```\n- indicate to retrieve\neverything below that\npath.\n\n```\n\"*\" - indicates to retrieve\nthe entire stored object.\n```\n```\nUID string If the object is associate with a\nuser, then the ID of the user\nshould be specied and forms a\ncompound key together with the\noid.\n```\n```\n* If you call this method through\nan external OAuth2 SDK, then\nthe UID may be passed implicitly\nwithin the access_token.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\n```\n\n```\nRequired Name Type Description\n```\n```\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The error\ncode and message is given within\nthe response data (see below). If\nthis parameter is set to true, the\nHTTP status code in SAP\nCustomer Data Cloud's response\nwould reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and A\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nshort textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.should not\nbe relied upon by your implementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.deleteSchemaFields REST\n\n## Description\n\nDeletes a eld from a specied Gigya Data Store schema type.\n\nOnce a eld is deleted:\n\n```\nYou cannot save data to that eld, nor retrieve data that was saved to that eld.\n```\n```\nYou cannot recreate a eld of the same name in the schema.\n```\nThis parameter or feature is part of our Early Adopters Program. To nd out if you are eligible for participation, contact your SAP\n\nCustomer Data Cloud Customer Engagement Executive or contact us at SAP Support.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\nA short textua\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package, contact your SAP\nCustomer Data Cloud Customer Engagement Executive or contact us at SAP Support.\n```\n\n## Request URL\n\n#### https://ds./ds.deleteSchemaFields\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ntype string The schema type dened in the\nData Store from which to delete\nelds.\n```\n```\ndataSchema array The elds to delete from the\nspecied Data Store type. For\nexample:\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\n```\n```\n[\"field1\",\"field2\"]\n```\n\n```\nRequired Name Type Description\n```\n```\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.get REST\n\n## Description\n\nRetrieves an object's or the specied datum from Gigya's Data Store.\n\n## Request URL\n\n#### https://ds./ds.get\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\noid string The ID of the object to retrieve.\n```\n```\ntype string A string indicating the type of the\nobject, equivalent to a name\nclassifying objects as being of\nthe same type; used in searches\nand when applying schemas.\n```\n```\nelds string A comma separated list of elds\nto retrieve. Acceptable values for\nthis parameter:\n```\n```\nData eld names,\nspecifying the the\ncomplete path, i.e.\nalbum.photo.photoTitle_t\n```\n```\nPartial eld names (elds\nthat contain only a part\nof the path to sub-\nobjects, i.e. album.photo)\n```\n- indicate to retrieve\neverything below that\npath.\n\n```\n\"*\" - indicates to retrieve\nthe entire stored object.\n```\n```\nUID string If the object is associate with a\nuser, then the ID of the user\nshould be specied and forms a\ncompound key together with the\noid.\n```\n```\n* If you call this method through\nan external OAuth2 SDK, then\nthe UID may be passed implicitly\nwithin the access_token.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n\n```\nRequired Name Type Description\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The error\ncode and message is given within\nthe response data (see below). If\nthis parameter is set to true, the\nHTTP status code in SAP\nCustomer Data Cloud's response\nwould reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ndata JSON object The object data retrieved from Gigya's Data\nStore.\n```\n```\noid string The ID of the object\n```\n```\nUID string If the object is associate with a user, then\nthe ID of the user.\n```\n```\nlastUpdated long The time of the latest change in this object,\nin Java time (number of milliseconds since\nJan. 1st 1970).\n```\n```\nlastUpdatedTime string The time of the latest change in this object,\nin ISO 8601 format.\n```\n```\ncreated long The time of this object's creation, in Java\ntime (number of milliseconds since Jan. 1st\n1970).\n```\n```\ncreatedTime string The time of this object's creation, in ISO\n8601 format.\n```\n### Response Example\n\n##### {\n\n```\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n},\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n```\n\n## ds.getSchema REST\n\n## Description\n\nThis method retrieves the schema of a specied data type in Gigya's Data Store (DS).\n\n## Request URL\n\n#### https://ds./ds.getSchema\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ntype string A string indicating the type of\nthe object, equivalent to a\nschema name. To see all the\n```\n```\n\"lastUpdatedTime\": \"2012-08-08T12:16:24Z\",\n\"lastUpdated\": 1344428184385,\n\"createdTime\": \"2012-08-08T12:16:24Z\",\n\"created\": 1344428184385,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"d02ada709b494be18d47cab5a23c3470\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nFor security reasons this method is not available for client-side SDKs, only for server-side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\nRequired Name Type Description\n\n```\ntypes currently dened in the\nschema, use ds.getTypes or the\nSchema Editor.\n```\n```\nlter string Species what parts of the\nschema to return, can be one of\nthe following options:\n```\n```\nfull - (default) return the\ncomplete schema\nincluding implicit elds\nand dynamic elds.\n```\n```\nexplicitOnly - return\nonly the parts of the\nschema that were\nexplicitly set by the\npartner using a\nsetSchema call.\n```\n```\nclientOnly - return only\nthe elds in the schema\nthat allow client access.\nFor those elds return\nonly the type and\nformat and required\nproperties (see the\nformat denition of the\nschema object).\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\n```\n\n```\nRequired Name Type Description\n```\n```\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n```\nincludeDynamicSchema Boolean Deprecated. When it is explicitly\nset to false it should be\ninterpreted as\nschemaType=explicit.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nschema JSON object A JSON object that details the schema\nstructure. See the format denition of the\nschema object.\n```\n### Response Example\n\n## ds.getTypes REST\n\n## Description\n\nThis method retrieves the schema data types dened in Gigya's Data Store (DS).\n\n##### {\n\n```\n\"schema\": {\n\"fields\": {\n\"customField1\": {\n\"type\": \"integer\"\n},\n\"customField2\": {\n\"type\": \"string\"\n},\n\"customField3\": {\n\"type\": \"string\"\n}\n},\n\"dynamicSchema\": false\n},\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"0d8382a314ac4329a53add3067e863d9\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n\n## Request URL\n\n#### https://ds./ds.getTypes\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n```\nFor security reasons this method is not available for client-side SDKs, only for server-side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ntypes array A list of the types which make up this DS\nschema.\n```\n### Response Example\n\n## ds.search REST\n\n## Description\n\nSearches and retrieves data from Gigya's Data Store (DS) using an SQL-like query. For security reasons this method is not\n\navailable for client side SDKs, only for server side SDKs. SQL queries are converted into Gigya's proprietary query language. SQL\n\ninjection attacks are not possible because queries are both created by the customer and then converted by Gigya.\n\nA short delay is possible between the writing of account data to the data base and its availability in queries.\n\n##### {\n\n```\n\"types\": [\n\"myType\"\n],\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"f293e7d275fa4656b6bf197d90027ae2\",\n\"time\": \"2017-08-17T07:32:49.229Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\n\nCustomer Engagement Executive or email support@gigya-inc.com.\n\n## Query Syntax Specication\n\nGigya queries use the same syntax rules as SQL, however not all standard SQL key words are available.\n\n```\nWhen querying for string values, value must be wrapped in double quotes. e.g., SELECT * FROM data.music WHERE guitar\n= \"Fender\".\n```\n```\nWhen querying for Integer (and other non-textual elds) values, value must not be wrapped in quotes. e.g., SELECT * FROM\ndata.userAccounts WHERE age = 42.\n```\n```\nUnsupported SQL syntax in the query string (e.g., HAVING) will produce an error.\n```\n```\nThe query string clauses must be ordered in the following way*:\n```\n```\n. Select clause\n```\n```\n. From clause\n```\n```\n. Where clause\n```\n```\n. Filter clause\n```\n```\n. Group By clause\n```\n```\n. Order By clause\n```\n```\n. Start clause Or/And Limit clause\n```\n```\nDeleted objects do not appear in queries.\n```\n```\nEncrypted elds are decrypted during searches but comparison operators (>, >=, <, <=) and regex expressions are not\navailable on these elds. The Contains keyword can be used for case-insensitive searches on encrypted elds but does not\nsupport partial strings.\n```\n```\nExample queries and responses can be viewed at DS.search Examples.\n```\nselect - The \"select\" statement accepts a comma separated list of elds or objects to retrieve. Acceptable values for this\n\nstatement are:\n\n```\nField names, specifying the complete path, i.e. data.album.photo.photoTitle_t. Specifying partial elds names (data.album)\nwill return all the elds in the path.\n```\n```\nObject names, specifying an object name, i.e. user_likes will return all the elds in the user_likes object.\n```\n```\nPartial eld names (elds that contain only a part of the path to sub-objects, i.e. data.album) - will retrieve everything below\nthat path.\n```\n```\n* - will retrieve every eld in the schema.\n```\n```\ncount(*) - Returns the number of objects for a particular object type in the data store. The result is given in the response as\na single value inside the \"data\" eld.\n```\n```\nas - create an alias (temporary title) for the returned object or eld. 'Select data.track.title as song...' will return a eld\ncalled track.song containing the values of data.track.title. Example:\n```\n```\n// Query\nSELECT data.music.trackName AS Track\n// Result\n{\"results\": [\n{\"track\": {\"song\": \"I will follow\"} },\n{\"track\": {\"song\": \"Into the Heart\"} },\n{\"track\": {\"song\": \"The Ocean\"} },\n{\"track\": {\"song\": \"A Day Without Me\"} },\n{\"track\": {\"song\": \"Shadows and Trees\"} }\n],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n```\n\n```\nsum(), min(), max(), avg(), sum_of_squares(), variance(), std() - Mathematical functions, must all be performed on the\nsame numeric eld. Fields with null values will be ignored.\n```\n```\nThe name of the eld on which the function is to be performed must be entered in the brackets. For example: 'Select\nmin(track) from data.music'.\n```\n```\nsum - provides a total for the eld in the brackets.\n```\n```\nmin/max - minimum/maximum value for the eld. If no values are found, min will return \"innity\" and max will\nreturn \"-innity\".\n```\n```\navg - average value of the eld.\n```\n```\nvariance - the extent that the eld's values vary.\n```\n```\nstd - standard deviation, the likelihood that values vary.\n```\nfrom - Name of the data source. Only one data source is supported. Queries on objects in the Data Store (DS.search) must specify\n\nthe object \"type\" classic ation as dened in the DS.store method.\n\nwhere - The \"where\" clause denes conditions for selecting items from the collection. Supported operators:\n\n```\n> , >=, <, <= , = , != - the left operand must be a data eld name (with a proper suffix letter) and the right operand must be a\nconstant of the same type as the eld. For example: \"where track.# >= 18 \".\n```\n```\nOnly = and != can be used with encrypted elds.\n```\n```\nand , or\n```\n```\ncontains, not contains - may be used only on text (string) elds and arrays.\n```\n```\nText (string) elds - support standard full text search capabilities. Contains is not case-sensitive. The left operand\nmust be a text eld name and the right operand must be a constant string. You can search for a specic word within\nthe string, for example: WHERE data.about_t CONTAINS \"music\". Underscores are treated as separators between\nwords. Contains cannot be used to locate words within encrypted elds (you must enter the full string) and is case\ninsensitive.\n```\n```\nArrays - the left operand must be an array eld name and the right operand must be a constant of the same type as\nthe array values. The array eld name must have a suffix denoting the type of the arrays values. For example:\nWHERE data.hobbies_s CONTAINS \"swimming\".\n```\n```\nin() - only retrieve items if the eld contains one of the list values. For example: 'select * from data.music where\ntrack.album_artist in (\"Elvis\", \"Beatles\", \"Santana\")' will return tracks recorded by the specied artists.\n```\n```\nis null , is not null\n```\n```\nnot\n```\n```\nregex ('') - denes a search term using regex formatting. Regex patterns cannot be used on encrypted elds.\n```\norder by - The \"order by\" clause species a list of elds by which to sort the result objects.\n\nlimit - Using the \"LIMIT\" clause, you may specify the maximum number of returned result objects. If not specied, the default is\n\n300. The maximum number of results that will be returned is 10000 ; setting a limit higher than 10000 will have no affect on\n\nnumber of results. If the search is sent with openCursor = true, LIMIT will set the batch size. LIMIT must be the last item in the\n\nquery.\n\n```\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\"\n}\n```\n###  Note\n\n```\nYou can only search words that are part of a sentence, you cannot search for parts of a word.\n```\n\nstart - The \"start\" clause (not an SQL standard clause) may be used for paging. The clause species the start index from which to\n\nreturn result objects.\n\nThe 'select - from - where - order by' query creates an (internal) indexed list of objects. By using the start & limit clauses, you will\n\nreceive a subset of this list, starting with the start index and ending with start+limit index.\n\n### Query Optimization\n\nBelow are a few points to note regarding query optimization:\n\n```\n. Query execution is based on clause position and is executed from left to right.\n```\n```\n. Place clauses that have the greatest impact on records returned at the beginning of your SQL statement. For example, to\nretrieve a list of male users over the age of 25:\n```\n```\nThis is because lt ering rst by gender automatically reduces the result set by half, so the server only needs to run the next\nlt er on half of the overall population.\n```\n```\n. A NOT clause (NOT or !) is executed on a single statement immediately to it's right, after analyzing the statement. A single\nstatement can hold several conditions inside parentheses.\n```\n```\n. Date ranges are calculated much more efficiently using a timestamp eld rather than a date eld.\n```\n```\n. Use of regex is computationally intensive and can signicantly increase response time.\n```\n```\n. AND clauses take precedence over OR clauses (i.e., AND clauses are executed before OR clauses).\n```\n```\n. Use parentheses to modify default precedence (e.g., to execute an OR operation before an AND operation).\n```\n### Pagination\n\nWhen running long queries (>5,000 records returned), it's best practice to paginate your results using cursors. If you do not use\n\ncursors, results are limited to a total of 5,000 records per query (not just per page).\n\nTo use cursors, during the rst request, pass query= and openCursor=true. The response will include the\n\nnextCursorId eld, containing a cursor ID to be used in the next request. On subsequent requests, pass cursorId= and do not submit the query again. The absence of the nextCursorId eld in a response indicates the end of the\n\nresult set.\n\nWhen using openCursor, you cannot use 'START'.\n\n###  Note\n\n```\nWhen implementing paging, there is no guarantee that there will be no duplications or that recently added data will show up in\nthe query results.\n```\n###  Note\n\n```\nAlways prefer accessing data objects directly using their IDs (with ds.get) rather than using search, whenever possible.\nAccessing data objects directly using their OIDs is faster and optimal for run-time.\n```\n```\nAfter data is published to the DS, building the indexes is done asynchronously for performance reasons, and may take\nup to one second to complete.\n```\n```\nPlease note, when using a cursor, the number of results in a batch (limit) is not guaranteed.\n```\n```\nWhen querying for large numbers of results (>500) it is Best Practice to use the openCursor and then the cursorId with\nthe nextCursorId value rather than attempting to page through results using timestamps of the user records.\n```\n```\nSELECT * FROM data.userAccounts where gender=\"male\" AND age > 25\n```\n\n## Request URL\n\n#### https://ds./ds.search\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\nquery string A SQL-like query specifying the\ndata to retrieve. Please refer to\nthe Query language\nspecication section above.\n```\n```\nquerySig string An HMAC_SHA1 signature\nproving that the search call is in\nfact coming from your client\napplication, in order to prevent\nfraud. Follow the instructions in\nConstructing a Signature using\nthe following base-string: query\n+ \"_\" + expTime. When using\ncursors, this parameter should\nonly be sent with the initial\nrequest and omitted from\nsubsequent requests.\n```\n```\nThis parameter is required only\nwhen calling the search method\nfrom client side (i.e., Mobile\nSDKs)\n```\n```\nexpTime string The GMT time when the\nquerySig parameter should\nexpire. The expected format is\nthe Unix time format (i.e., the\nnumber of seconds since Jan.\n1st 1970). Gigya checks the time\nwhen the search request is\nreceived. If the time succeeds\nexpTime, the request is\nconsidered forged.\n```\n\nRequired Name Type Description\n\n```\nThis parameter is required only\nwhen calling the search method\nfrom client side (i.e., Mobile\nSDKs)\n```\n```\nopenCursor Boolean When set to true, the search\nresponse will include, in\naddition to the rst page,\nanother eld named\nnextCursorId, which is used to\nfetch the next batch of results.\nThis parameter should only be\nused on the rst request and\nlater should be removed from\nthe request. When openCursor\nis true, the Limit clause sets the\nnumber of results returned in\nthe batch.\n```\n```\ncursorId string The cursor ID that contains the\nnextCursorId value received in\nthe rst search call. Note: You\ncannot pass both cursorId and\nquery on the same request -\ncursorId brings the next page\nfor the search for which it was\nopened. Also, the time between\nsearch requests using a\ncursorId must not exceed 5\nminutes.\n```\n```\ntimeout integer The timeout for the request (in\nmilliseconds). Default value is\n20000 (20 seconds). Maximum\n```\n###  Note\n\n```\nYou cannot use a cursor if\nyou have a 'group by' or\nwhen using 'start'.\n```\n###  Note\n\n```\nEach request should contain\na different cursorId obtained\nfrom the response of the\nprevious request (not the\nrst) using the nextCursorId\neld. The exception to this\nrule is when a request fails\nor when a particular result\nset needs to be resent; in\nthis case, resend the same\ncursorID (as long as it has\nnot expired) to receive its\nassociated result set.\n```\n\n```\nRequired Name Type Description\n```\n```\nallowed value is 60000 (60\nseconds).\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ndata Array An array of data objects retrieved from the\nDS.\n```\n```\nobjectsCount integer The number of objects returned in the\n\"data\" array.\n```\n```\ntotalCount integer The total number of object that satisfy the\nquery in the DB. This is useful for knowing\nhow many objects are in the DB, when\nfetching limited amount using the \"limit\"\nparameter.\n```\n```\nnextCursorId string Used to fetch the next batch of results. This\nparameter is not returned on the last batch\nof results, its absence means that the result\nset is nished.\n```\n### Response Example\n\n##### {\n\n```\n\"results\": [{\n\"oid\": \"050\",\n\"lastUpdated\": 1344151787611,\n\"lastUpdatedTime\": \"2012-08-05T07:29:47Z\",\n\"created\": 1344151532974,\n\"createdTime\": \"2012-08-05T07:25:32Z\",\n\"data\": {\n\"FN\": 7,\n\"Fn\": 7,\n```\n\n\"field1\": 7,\n\"field2\": 7,\n\"field3\": 7,\n\"field4\": \"7\",\n\"field5\": \"7\",\n\"field6\": \"7\",\n\"field7\": \"7\",\n\"field8\": \"7\",\n\"field10\": \"d1_0\",\n\"field11\": \"d1_0\",\n\"field12\": \"d1_0\",\n\"field13\": \"d1_0\",\n\"fn\": 7\n}},\n{\n\"oid\": \"1c675e20f7724c93b9ca82aa7b206b41\",\n\"lastUpdated\": 1344172297960,\n\"lastUpdatedTime\": \"2012-08-05T13:11:37Z\",\n\"created\": 1344172297960,\n\"createdTime\": \"2012-08-05T13:11:37Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"UID\": \"_gid_t6BWv8yeJG6QZyq7Wtav1Q==\",\n\"oid\": \"51b5d8e72c664520a27c7020ff2f1494\",\n\"lastUpdated\": 1344414722808,\n\"lastUpdatedTime\": \"2012-08-08T08:32:02Z\",\n\"created\": 1344414722808,\n\"createdTime\": \"2012-08-08T08:32:02Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"677cc8b3437b40959b9b1288add0a2ec\",\n\"lastUpdated\": 1344172153286,\n\"lastUpdatedTime\": \"2012-08-05T13:09:13Z\",\n\"created\": 1344172153286,\n\"createdTime\": \"2012-08-05T13:09:13Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n\"lastUpdated\": 1344428184385,\n\"lastUpdatedTime\": \"2012-08-08T12:16:24Z\",\n\"created\": 1344428184385,\n\"createdTime\": \"2012-08-08T12:16:24Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\n\n## More Information\n\nds.search Examples\n\n## ds.search Examples REST\n\n## Description\n\nThis page shows examples using the ds.search REST API.\n\n## Examples\n\n```\n. Examples of searching objects by UID:\n```\n```\n1.1 First associate an object to a UID using ds.store:\n```\n```\n1.2 Search objects by UID:\n```\n```\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"super1\",\n\"lastUpdated\": 1344172332701,\n\"lastUpdatedTime\": \"2012-08-05T13:12:12Z\",\n\"created\": 1344172332701,\n\"createdTime\": \"2012-08-05T13:12:12Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}}],\n\"objectsCount\": 9,\n\"totalCount\": 9,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"fb5e8b258afc4016ad454cc9fd1d64ec\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n```\nds.store({\ndata:{bands:{rock:'zeppelin', jazz:'coltrain'}},\ntype:'music',\noid:'auto',\nUID='_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM='\n});\n```\n```\nSELECT * FROM music WHERE UID='_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM='\n```\n\n```\n1.3 Response to the query:\n```\n. Example of a count of objects:\n\n```\nResponse to the query:\n```\n. Example of a query using limit and start. The query lists 3 elds in a music object where the musician is \"U2\". The query is\nlimited to 5 results, starting with the 100th valid user.\n\n```\nResponse to the query:\n```\n. Example of a query using as. The query lists 3 elds in a music object where the musician is \"U2\". The query will return 5\nresults, starting with the 100th valid user.\n\n```\nResponse to the query:\n```\n##### {\n\n```\n\"results\": [\n{\n\"data\": {\n\"bands\": {\n\"jazz\": \"coltrain\",\n\"rock\": \"zeppelin\"\n}\n},\n\"lastUpdated\": 1419426021590,\n\"created\": 1419426021590,\n\"lastUpdatedTime\": \"2014-12-24T13:00:21Z\",\n\"createdTime\": \"2014-12-24T13:00:21Z\",\n\"UID\": \"_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM=\",\n\"oid\": \"3dfaa6836ac64711837cb98e3893007a\"\n}\n],\n\"objectsCount\": 1,\n\"totalCount\": 1,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"d126af8d2d21446d867fa67f61cef832\"\n}\n```\n```\nSELECT COUNT(*) FROM music\n```\n```\n{\"results\": [{ \"count(*)\": 1527}],\n\"objectsCount\": 1,\n\"totalCount\": 1527,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"11111\"}\n```\n```\nSELECT music.trackName, music.album, music.format FROM music WHERE music.musician=\"U2\" LIMIT\n```\n```\n{\"results\": [\n{\"music\": {\"trackName\": \"I will follow\", \"format\": \"mp3\"} },\n{\"music\": {\"trackName\": \"Into the Heart\", \"album\": \"Boy\", \"format\": \"mp3\" } },\n{\"music\": {\"trackName\": \"The Ocean\", \"album\": \"Boy\" } },\n{\"music\": {\"trackName\": \"A Day Without Me\", \"album\": \"Boy\", \"format\": \"mp3\" } },\n{\"music\": {\"trackName\": \"Shadowns and Tall Trees\", \"album\": \"Boy\", \"format\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\nSELECT music.trackName AS Track, music.album AS Disk, music.format AS Extension FROM music WH\n```\n\n```\nResponse to the query:\n```\n. Example of a query using contains. This query counts pictures of \"Madrid\":\n\n```\nResponse to the query\n```\n. Example of a query using regex. This query searches for photos starting with the letter \"A\".\n\n```\nResponse to the query:\n```\n```\n{\"results\": [\n{\"music\": {\"Track\": \"I will follow\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Into the Heart\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"The Ocean\", \"Disk\": \"Boy\" } },\n{\"music\": {\"Track\": \"A Day Without Me\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Shadows and Trees\",\"Disk\": \"Boy\", \"Extension\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\n{\"results\": [\n{\"music\": {\"Track\": \"I will follow\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Into the Heart\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"The Ocean\", \"Disk\": \"Boy\" } },\n{\"music\": {\"Track\": \"A Day Without Me\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Shadows and Trees\",\"Disk\": \"Boy\", \"Extension\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\nSELECT COUNT(*) FROM album WHERE album.photo.title CONTAINS \"Madrid\"\n```\n```\n{ \"results\": [ { \"count(*)\": 28 } ],\n\"objectsCount\": 1,\n\"totalCount\": 28,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"3333\" }\n```\n```\nSELECT album.photo.title FROM album WHERE album.photo.title = regex('A.*')\n```\n##### {\n\n```\n\"results\": [{\n\"album\": {\n\"photo\": {\n\"title:\"At the party\",\n\"title\": \"At the sea\",\n\"industry\": \"Computer Software\" }\n}\n}, {\n\"profile\": {\n\"name\": \"Andy Goslan\",\n\"religion\": \"Atea\",\n\"industry\": \"Computer Software\" }\n}\n],\n\"objectsCount\": 2,\n\"totalCount\": 2,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n```\n\n## ds.setSchema REST\n\n## Description\n\nThis method allows specifying a schema for a data type in Gigya's Data Store (DS). The schema sets eld names, data types,\n\nformatting and encryption as well as client side access restrictions. Data object schemas act as meta-data, guiding Gigya how to\n\nhandle the data in the specied elds.\n\n```\nDepending on schema setting, other elds can be added to the storage outside the schema, Gigya will add them as is\nwithout special treatment.\n```\n```\nField deletion: a eld in the Data object schema is eligible for deletion if no data has been saved to it. To delete a eld in the\nschema call ds.deleteSchemaFields.\n```\n```\nChanges to schema are incremental, when setting the schema for part of the elds, the properties of the omitted elds\nremain unchanged.\n```\n```\nUnless specied otherwise, schema dened elds are only accessible from the server.\n```\n## Request URL\n\n#### https://ds./ds.setSchema\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\n\"callId\": \"1234567\"\n}\n```\n###  Note\n\n```\nFor security reasons this method is not available for client side SDKs, only for server side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n```\nRequired Name Type Description\n```\n```\ntype string A string indicating the type of\nthe object, equivalent to a\nschema name. The objective of\nthis eld is to classify objects as\nsharing the same schema.\n```\n```\ndataSchema JSON object A JSON object dening the\nschema to be set. See the\nformat denition of the Schema\nObject, below.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Schema Object\n\n```\nField Type Description\n```\n```\nelds JSON object This object denes properties per data\nelds. The object contains eld names and\ntheir corresponding list of properties (see\nthe example below). The eld name should\nbe the full path name with dots, i.e.\n\"work.address\".\n```\n```\nThe properties in option are:\n```\n```\ntype - Denes the data type of this\neld. The supported values are\n\"integer\", \"oat\", \"boolean\",\n\"string\", \"date\", \"long\", \"text\" and\n\"binary\".\n```\n```\nWhen the 'type' property is not\nspecied the type will be deduced\nfrom the eld name extension or\nautomatically according to the\ncontent of the rst item. When\ndening a 'binary' eld type, it is not\ninferred from the data must be\ndeclared explicitly through the\n'type' parameter.\n```\n```\nPlease note that eld's type cannot\nbe changed after it contains data.\n```\n```\nwriteAccess - Species whether to\nallow unsigned requests to write\ninto this eld. The supported values\nare:\n```\n```\n\"serverOnly\" (default ) -\nOnly signed requests\ncoming from the server are\nallowed.\n```\n```\n\"clientCreate\" - Unsigned\nrequests coming from the\nclient are allowed to write\ninto this eld, only if it\nwasn't set before.\n```\n```\n\"clientModify\" - Unsigned\nrequests coming from the\nclient are allowed to write\ninto this eld and modify\nexisting values.\n```\n```\nformat - Allows assigning a regular\nexpression that denes the format\nof this data eld. Gigya will verify\nthat data set in this data eld\nmatches the format. If the data set\nin this eld doesn't match the\nformat, Gigya will not set the data\n```\n\nField Type Description\n\n```\nand will return an error. The best\npractice is to validate the data\nformat on your client application.\nThe format property accepts a\nstring of the form: \"regex('')\". The\nregex syntax can be found in:\nRegular Expression Language\nReference.\n```\n```\nlanguages - An array of strings\ncontaining languages with which a\ntext eld is compatible, in addition\nto the default languages. A\nmaximum of four such languages\nare supported. The values passed in\nthis property are added to the\nexisting languages in the eld, and if\nthe total number exceeds four\nlanguages, the operation fails.\n```\n```\nencrypt - May be applied to string,\nbasic-string. Passing a value of\n'AES' (the encryption standard\napplied) sets the eld to encrypted.\nWhen string elds are encrypted,\nyou may use them in a search (e.g.\nusing accounts.search) only by\npassing an exact match (such as x =\n\"ABCDE\"), and not partial matches\n(x CONTAINS \"ABC\"). String search\nvalues are case sensitive.\n```\n```\nIf you set the encrypt\nproperty on a eld that\nalready contains data, the\nexisting data will remain un-\nencrypted. Only new data\nwill be encrypted.\n```\n```\nOnce a eld is set to\nencrypt, it cannot be\nundone.\n```\n```\nTo encrypt a eld that is not\nstring or basic-string, use\nthe\nencryptedNonSearchable\nparameter instead\n```\n```\nTo delete a eld from the schema, you\nmust ensure that data has never been\nsaved to it (even if said data has been\ndeleted), it has no dened type, and then\n```\n###  Note\n\n```\nThe only language currently\nsupported for this functionality\nis Japanese.\n```\n\n```\nField Type Description\n```\n```\nset it to null (see \"eld6\" in the example\nbelow). Saving data to a eld automatically\nassigns a type.\n```\n```\nSetting a eld's properties to null will reset\nthe writeAccess property to \"serverOnly\"\n(without deleting the eld), if the eld\ncontains/contained data and/or has a type\nsetting.\n```\n```\ndynamicSchema Boolean Species whether the schema is strict or\ndynamic. The default value of this\nparameter is true i.e. dynamic schema. In a\ndynamic schema you may add new elds\nthat are not dened in the schema to the\nDS. The new elds are automatically added\nto the dynamic schema. In a strict schema\nyou can only write into elds that are\nalready dened in the schema.\n```\n## Schema Object Example\n\n## Sample Requests\n\n##### {\n\n```\nfields: {\n\"field1\": {\nwriteAccess:\"clientCreate\",\nformat:\"regex('/^[a-z0-9_-]{3,16}$/')\"\n},\n\"field4\": {\ntype:\"float\"\n},\n\"field5\": {\ntype:\"string\",\nencrypt:\"AES\"\n},\n\"field6\": null,\n\"field7\": {\ntype:\"text\",\nlanguages:[\"ja\"]\n}\n},\ndynamicSchema: false\n}\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.store REST\n\n## Description\n\nStores an object data in SAP Customer Data Cloud's Data Store (DS). The Data Store is only available for use with fully registered\n\naccounts.\n\n## Request URL\n\n#### https://ds./ds.store\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide. The DS is part of the Customer Identity\npremium package that requires separate activation. If the DS is not part of your site package contact your SAP Customer Data\nCloud Customer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ndata JSON object Species the data to store. The data object\nshould be specied as a JSON object\ncomplying with the following restrictions:\n```\n```\nA maximum size of 512K of data.\n```\n```\nUser dened eld names must\nbegin with a character and may\ncontain characters, digits and\nunderscores.\n```\n```\nWe highly recommend that you give\nevery eld a type specication by\nappending the type to the eld\nname in the following manner: \"_\".\nValid types are:\n```\n```\ni - an integer number (may\ncontain 64bit long values\nas well), allows exact\nmatching or range\nsearches.\n```\n```\nf - a oating point number,\nallows exact matching or\nrange searches.\n```\n```\ns - a string only allows\nexact matching.\n```\n```\nt - a full text search eld,\nallows for partial searching\nbased on keywords.\n```\n```\nb - Boolean.\n```\n```\nd - a date eld, allows exact\nmatching or range\nsearches. The valid date\nformats are:\n```\n```\nStandard ISO time\nformat (like \"2011-\n07-\n14T11:42:32.123+3\",\nmay be specied\n```\n\nRequired Name Type Description\n\n```\nwithout a time at all\nor without a time\nzone)\n```\n```\n\"YYYY-MM-DD\nHH:MM:SS\"\n```\n```\nWhen the eld type is not specied\nexplicitly we will try to auto detect\nit. Fields that fail auto detection will\nbe considered strings.\n```\n```\nFor example:\n```\n```\n{ rstName_s : \"david\", birthDate_d : \"1978-\n07-22\", about_t : \"I love tracking,...\",\nacademicDegree : { university_s:\n\"Berkeley\", degree_s: \"MBA\",\ndepartment_s: \"Business\", courses : [{...},\n{...},...] }, hobbies_s: [\"running\", \"music\",\n\"movies\"]}\n```\n```\nImportant\n```\n```\nWhen saving data as a nested eld, it is\nimportant to save the object in the format\nbelow:\n```\n```\nand not as:\n```\n```\nDS always returns an object as it was\nsubmitted, this is different than other SAP\nCustomer Data Cloud schemas, which\nexpand nested objects automatically.\n```\n```\ntype string A string indicating the type of the object,\nequivalent to a name classifying objects as\nbeing of the same type; used in searches\nand when applying schemas.\n```\n###  Note\n\n```\nWhen dening a 'binary' eld\ntype, it is not inferred from the\ndata, and must be set explicitly\nusing the 'setSchema' method.\n```\n```\n// Correct\n{\n'a': {\n'b': 'value'\n}\n}\n```\n```\n// Incorrect\n{\na.b:'value'\n}\n```\n\n```\nRequired Name Type Description\n```\n```\noid string A unique object identier. If this parameter\nis set with the \"auto\" value, SAP Customer\nData Cloud will generate a unique ID for the\nobject.\n```\n```\nUID string A unique ID of a user. Setting this\nparameter associates the data object with\nthe specied user. The identier of this\nobject is the compound of oid and UID.\n```\n```\nupdateBehavior string This parameter denes how to handle\nconicting updates. The parameter may\nreceive one of the following values:\n```\n```\n\"arrayPush\" (default) - will cause\narrays data provided with this API\ncall to be appended to existing\narrays data in the DB.\n```\n```\n\"arraySet\" - will replace the content\nof existing arrays data in the DB\nwith the values of arrays data\nprovided with this API call.\n```\n```\n\"replace\" - will cause the entire\nobject data in the DB to be\nreplaced with the new data\nprovided with this call.\n```\n```\nformat string Determines the format of the response.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to pass data\nthrough the current method and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases to\nsuppress logic applied by the Web SDK,\nsuch as automatic opening of screens (e.g.,\nin a registration completion scenario). This\nparameter may not be used with REST\nAPIs.\n```\n```\nhttpStatusCodes Boolean The default value of this parameter is false,\nwhich means that the HTTP status code in\nSAP Customer Data Cloud's response is\nalways 200 (OK), even if an error occurs.\nThe error code and message is given within\nthe response data (see below). If this\nparameter is set to true, the HTTP status\ncode in SAP Customer Data Cloud's\nresponse would reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\noid string The object's unique identier. The value is\neither the oid parameter that you specied\nin the API call or a unique string generated\nby SAP Customer Data Cloud (if you have\nset the parameter to be \"auto\").\n```\n### Response Example\n\n##### {\n\n```\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"bcb794e7b8ca41b1b3baf99e7bc1c86a\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```",[],[230,247],{"_104":255,"_97":256,"_163":257,"_165":231,"_166":145,"_167":144,"_169":118,"_106":258,"_101":259,"_171":241,"_173":260,"_174":22,"_175":-5,"_176":261,"_100":262},"fa4d6be4-129e-11f1-ac32-42dde27851f2","groups.md","63a65396-129d-11f1-917c-42dde27851f2",["D",1772060943847],3,"## accounts.groups.finalizeInvitation REST\n\nThis API finalizes the group invitation by adding the user to the group.\n\n### Request URL\n\n##### https://accounts./accounts.groups.finalizeInvitation\n\nWhere is:\n\n##### us1.gigya.com - For the US data center.\n\n##### eu1.gigya.com - For the European data center.\n\n##### au1.gigya.com - For the Australian data center.\n\n##### eu2.gigya.com - For the European Azure data center.\n\n##### cn1.sapcdm.cn - For the Chinese data center.\n\n##### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n### Parameters\n\n###### {\n\n```\n\"callId\": \"26254b038410468bb5a3a344134fd88b\",\n\"errorCode\": 0,\n\"apiVersion\": 2,\n\"statusCode\": 200,\n\"statusReason\": \"OK\",\n\"time\": \"2018-12-11T12:52:24.250Z\"\n}\n```\n####  Note\n\n```\nPrior to calling this API, make sure to set the “invitation URL” by calling accounts.groups.setSiteConfig REST.\n```\n####  Note\n\n```\nCertain APIs are not supported on all data centers. The specific API documentation will define if there are any data center\nrestrictions for the API.\n```\n\n```\nRequired Name Type Description\n```\n```\ntoken string The invitation token.\n```\n```\nuid string The user ID assigned to the group invitation.\n```\n```\nThe uid or login_token are required.\n```\n```\nlogin_token string The login token for the user assigned to the group invitation.\n```\n```\nThe uid or login_token are required.\n```\n```\nformat string Determines the format of the response.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to pass data through the current method and return it,\nunchanged, within the response.\n```\n```\nhttpStatusCodes Boolean The default value of this parameter is false, which means that the HTTP status code in\nSAP Customer Data Cloud's response is always 200 (OK), even if an error occurs. The\nerror code and message is given within the response data (see below). If this parameter is\nset to true, the HTTP status code in SAP Customer Data Cloud's response would reflect an\nerror, if one occurred.\n```\n### Authorization Parameters\n\nEach REST API request must contain identification and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n##### accounts.login\n\n##### socialize.login\n\n##### accounts.notifyLogin\n\n##### socialize.notifyLogin\n\n##### accounts.finalizeRegistration\n\n##### accounts.linkAccounts\n\nPlease refer to the Authorization Parameters section for details.\n\n### Sample Requests\n\n####  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n### Response Data\n\n```\nName Type Description\n```\n```\napiVersion integer Defines the API version that returned the response and may not always be available.\n```\n```\ncallId string Unique identifier of the transaction, for debugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a\ncomplete list of error codes, see the Error Codes table.\n```\n```\nerrorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.\n```\n```\nerrorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will\nappear in the response only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered the response. This is an internally used parameter that is not always\nreturned and should not be relied upon by your implementation.\n```\n```\ntime string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or 2021-03-\n05T06:11:31.513Z\n```\n```\nstatusCode integer The HTTP response code of the operation. Code '200' indicates success.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n\n```\nName Type Description\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n```\nmodel string The group's model.\n```\n```\ngroupId string The group's ID.\n```\n### Response Example\n\n## accounts.groups.getAllMemberGroups REST\n\nReturns the user's groups.\n\n### Request URL\n\n##### https://accounts./accounts.groups.getAllMemberGroups\n\nWhere is:\n\n##### us1.gigya.com - For the US data center.\n\n##### eu1.gigya.com - For the European data center.\n\n##### au1.gigya.com - For the Australian data center.\n\n##### eu2.gigya.com - For the European Azure data center.\n\n##### cn1.sapcdm.cn - For the Chinese data center.\n\n##### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n### Parameters\n\n###### {\n\n```\n\"callId\": \"17e71c8375614cd1bfe55a4e0122c049\",\n\"errorCode\": 0,\n\"apiVersion\": 2,\n\"statusCode\": 200,\n\"statusReason\": \"OK\",\n\"time\": \"2022-06-14T15:10:44.042Z\",\n\"model\": \"Family\",\n\"groupId\": \"Gur\"\n}\n```\n####  Note\n\n```\nCertain APIs are not supported on all data centers. The specific API documentation will define if there are any data center\nrestrictions for the API.\n```\n\n```\nRequired Name Type Description\n```\n```\nUID string The SAP Customer Data Cloud UID of the user.\n```\n```\nThe UID is optional if you pass the login token otherwise it is required.\n```\n```\nformat string Determines the format of the response.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to pass data through the current method and return it,\nunchanged, within the response.\n```\n```\nhttpStatusCodes Boolean The default value of this parameter is false, which means that the HTTP status code in\nSAP Customer Data Cloud's response is always 200 (OK), even if an error occurs. The\nerror code and message is given within the response data (see below). If this parameter is\nset to true, the HTTP status code in SAP Customer Data Cloud's response would reflect an\nerror, if one occurred.\n```\n### Authorization Parameters\n\nEach REST API request must contain identification and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n##### accounts.login\n\n##### socialize.login\n\n##### accounts.notifyLogin\n\n##### socialize.notifyLogin\n\n##### accounts.finalizeRegistration\n\n##### accounts.linkAccounts\n\nPlease refer to the Authorization Parameters section for details.\n\n### Sample Requests\n\n####  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n### Response Data\n\n```\nName Type Description\n```\n```\napiVersion integer Defines the API version that returned the response and may not always be available.\n```\n```\ncallId string Unique identifier of the transaction, for debugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a complete\nlist of error codes, see the Error Codes table.\n```\n```\nerrorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.\n```\n```\nerrorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will\nappear in the response only in case of an error.\n```\n```\ntime string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or 2021-03-\n05T06:11:31.513Z\n```\n```\nstatusCode integer The HTTP response code of the operation. Code '200' indicates success.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n\n```\nName Type Description\n```\n```\nresults array An array of groups the user is a member of, with the user's membership details.\n```\n### Response Example\n\n## accounts.groups.getAllModels REST\n\nThis API returns all existing models for the requested API key.\n\n### Request URL\n\n##### https://accounts./accounts.groups.getAllModels\n\nWhere is:\n\n##### us1.gigya.com - For the US data center.\n\n##### eu1.gigya.com - For the European data center.\n\n##### au1.gigya.com - For the Australian data center.\n\n##### eu2.gigya.com - For the European Azure data center.\n\n##### cn1.sapcdm.cn - For the Chinese data center.\n\n##### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n###### {\n\n```\n\"callId\": \"b42093126efa4c0fb8f9651a570a928c\",\n\"errorCode\": 0,\n\"apiVersion\": 2,\n\"statusCode\": 200,\n\"statusReason\": \"OK\",\n\"time\": \"2022-08-17T13:57:05.305Z\",,\n\"results\": [\n{\n\"groupId\": \"123\",\n\"model\": \"OrgModel111\",\n```\n```\n\"relationshipData\": {},\n\"memberSince\": \"2022-08-16T14:54:04.486Z\",\n\"lastUpdated\": \"2022-08-16T14:54:04.486Z\",\n\"memberSinceTimestamp\": 1660661644486,\n\"lastUpdatedTimestamp\": 1660661644486,\n\"permissions\": \"groupRead,groupWrite,groupDelete\",\n\"groupData\": {\n\"zipcode\": \"123456\",\n\"country\": \"Israel\",\n\"membersLimit\": 300,\n\"city\": \"Tel Aviv\",\n\"streetaddress\": \"street1\",\n\"source\": \"IMPORT\",\n\"state\": \"Israel\",\n\"type\": \"CUSTOMER\"\n}\n}\n]\n}\n```\n\n### Parameters\n\n```\nRequired Name Type Description\n```\n```\nincludeEmailTemplates boolean This parameter is optional, if true the model's groupInviteConfig data is included in the\nresponse.\n```\n### Authorization Parameters\n\nEach REST API request must contain identification and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n##### accounts.login\n\n##### socialize.login\n\n##### accounts.notifyLogin\n\n##### socialize.notifyLogin\n\n##### accounts.finalizeRegistration\n\n##### accounts.linkAccounts\n\nPlease refer to the Authorization Parameters section for details.\n\n### Sample Requests\n\n####  Note\n\n```\nCertain APIs are not supported on all data centers. The specific API documentation will define if there are any data center\nrestrictions for the API.\n```\n####  Note\n\n```\nFor details on the group invitation flow, see the Group Invitation section on the Email\nTemplates page.\n```\n####  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n### Response Data\n\n```\nName Type Description\n```\n```\napiVersion integer Defines the API version that returned the response and may not always be returned.\n```\n```\ncallId string Unique identifier of the transaction, for debugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a\ncomplete list of error codes, see the Error Codes table.\n```\n```\nerrorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.\n```\n```\nerrorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will\nappear in the response only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered the response. This is an internally used parameter that is not always\nreturned and should not be relied upon by your implementation.\n```\n```\ntime string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or 2021-03-\n05T06:11:31.513Z\n```\n```\nstatusCode integer The HTTP response code of the operation. Code '200' indicates success.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n\n```\nName Type Description\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only returned for backward compatibility.\n```\n```\nmodels array An array containing all the existing models for the requested API key.\n```\n```\nmodel - Model name\n```\n```\nselfProvisioning - If true the group based on this model can be created by users, otherwise users can\nnot create a new group based on this model.\n```\n```\ngroupInviteConfig - The group invitation configuration details. The configuration details will be\nreturned if includeEmailTemplates is set to true in the parameters.\n```\n### Response Example\n\n###### {\n\n```\n\"callId\": \"dbc9910f05a246878d128c50773e180b\",\n\"errorCode\": 0,\n\"apiVersion\": 2,\n\"statusCode\": 200,\n\"statusReason\": \"OK\",\n\"time\": \"2022-06-20T09:22:18.362Z\",\n\"models\": [\n{\n\"model\": \"Model 2\",\n\"selfProvisioning\": false,\ngroupInviteConfig: {\n\"landingPage\": \"http://localhost/melodi\",\n\"expiration\": 300,\n\"defaultLang\": \"en\",\n\"emailTemplates\": {\n\"en\": \"/accounts.groups.getGroupInfo\n\nWhere is:\n\n##### us1.gigya.com - For the US data center.\n\n##### eu1.gigya.com - For the European data center.\n\n##### au1.gigya.com - For the Australian data center.\n\n##### eu2.gigya.com - For the European Azure data center.\n\n##### cn1.sapcdm.cn - For the Chinese data center.\n\n##### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n### Parameters\n\n```\nRequired Name Type Description\n```\n```\nmodel string The model this group is based upon.\n```\n```\ngroupId string The groupId of the group to return.\n```\n### Authorization Parameters\n\nEach REST API request must contain identification and authorization parameters.\n\n###### ]\n\n###### }",[],[230,256],[230],{"_104":265,"_97":266,"_163":267,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":268,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_176":269,"_100":313},"c4cb0d5a-1299-11f1-935e-42dde27851f2","dsviewer","019c96ee-0299-75ff-a0e5-0acfa7a4e1a6",["D",1772058706545],[270,307],{"_104":271,"_97":180,"_163":272,"_165":267,"_166":145,"_167":168,"_169":118,"_106":273,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_176":274,"_100":306},"c4cae1ae-1299-11f1-935e-42dde27851f2","019c96ee-0299-75ff-a0e5-01618671f6df",["D",1772058706545],[275,283,291,298],{"_104":276,"_97":277,"_163":278,"_165":272,"_166":145,"_167":168,"_169":118,"_106":279,"_101":33,"_171":189,"_173":280,"_174":22,"_175":-5,"_176":281,"_100":282},"c4ca6120-1299-11f1-935e-42dde27851f2","DSViewer.tsx","019c96ee-0298-70c4-b317-63db012e7190",["D",1772058706545],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface DSViewerProps {\n type: string;\n data: any[];\n schema: any;\n totalCount: number;\n currentPage: number;\n limit: number;\n search: string;\n}\n\nfunction formatValue(value: any, maxLength: number = 100): { display: string; full?: string } {\n if (value === null || value === undefined) {\n return { display: \"null\" };\n }\n \n if (typeof value === \"object\") {\n const jsonStr = JSON.stringify(value, null, 2);\n if (jsonStr.length > maxLength) {\n return {\n display: `${jsonStr.substring(0, maxLength)}...`,\n full: jsonStr\n };\n }\n return { display: jsonStr };\n }\n \n const str = String(value);\n if (str.length > maxLength) {\n return {\n display: `${str.substring(0, maxLength)}...`,\n full: str\n };\n }\n \n return { display: str };\n}\n\nfunction getFieldsFromData(data: any[]): string[] {\n const fields = new Set();\n \n // Always include metadata fields\n fields.add(\"oid\");\n fields.add(\"created\");\n fields.add(\"lastUpdated\");\n \n // Extract fields from data objects\n data.forEach(item => {\n if (item.data && typeof item.data === \"object\") {\n Object.keys(item.data).forEach(key => fields.add(`data.${key}`));\n }\n if (item.UID) fields.add(\"UID\");\n });\n \n return Array.from(fields).sort();\n}\n\nfunction getNestedValue(obj: any, path: string): any {\n return path.split('.').reduce((current, key) => {\n return current && current[key] !== undefined ? current[key] : null;\n }, obj);\n}\n\nexport function DSViewer({ type, data, schema, totalCount, currentPage, limit, search }: DSViewerProps) {\n const fields = getFieldsFromData(data);\n const totalPages = Math.ceil(totalCount / limit);\n \n return (\n

{type} Data

\n Showing {data.length} of {totalCount} items\n {search && ` (filtered by \"${search}\")`}\n

\n \n {/* Pagination */}\n {totalPages > 1 && (\n

\n {currentPage > 1 && (\n \n Previous\n \n )}\n \n \n Page {currentPage} of {totalPages}\n \n \n {currentPage < totalPages && (\n \n Next\n \n )}\n

\n )}\n

\n\n {data.length === 0 ? (\n

No data found

\n {search ? `No items match \"${search}\"` : `No items in ${type}`}\n

\n ) : (\n

\n \n \n \n {fields.map(field => (\n \n ))}\n \n \n \n \n {data.map((item, index) => (\n \n {fields.map(field => {\n const value = getNestedValue(item, field);\n const formatted = formatValue(value);\n \n return (\n \n );\n })}\n \n \n ))}\n \n

\n {field}\n	Actions
\n {formatted.full ? (\n \n {formatted.display}\n \n ) : (\n {formatted.display}\n )}\n	\n \n \n Edit\n \n \n Delete\n \n \n

\n )}\n\n {/* Schema Information */}\n {schema && (\n

\n View Schema Information\n

\n {JSON.stringify(schema, null, 2)}\n

\n )}\n

\n );\n}",[],[266,180,277],{"_104":284,"_97":285,"_163":286,"_165":272,"_166":145,"_167":168,"_169":118,"_106":287,"_101":33,"_171":189,"_173":288,"_174":22,"_175":-5,"_176":289,"_100":290},"c4ca82b8-1299-11f1-935e-42dde27851f2","DataForm.tsx","019c96ee-0298-70c4-b317-667bc5e64a6b",["D",1772058706545],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface DataFormProps {\n type: string;\n schema: any;\n data?: any;\n}\n\nfunction getFieldType(fieldName: string, fieldSchema: any): string {\n if (fieldSchema?.type) {\n switch (fieldSchema.type) {\n case \"integer\":\n case \"long\":\n return \"number\";\n case \"float\":\n return \"number\";\n case \"boolean\":\n return \"checkbox\";\n case \"date\":\n return \"datetime-local\";\n case \"text\":\n case \"string\":\n default:\n return \"text\";\n }\n }\n \n // Infer from field name suffix\n if (fieldName.endsWith(\"_i\") || fieldName.endsWith(\"_l\")) return \"number\";\n if (fieldName.endsWith(\"_f\")) return \"number\";\n if (fieldName.endsWith(\"_b\")) return \"checkbox\";\n if (fieldName.endsWith(\"_d\")) return \"datetime-local\";\n \n return \"text\";\n}\n\nfunction getFieldValue(data: any, fieldPath: string): any {\n if (!data) return \"\";\n \n const parts = fieldPath.split(\".\");\n let value = data;\n \n for (const part of parts) {\n if (value && typeof value === \"object\" && part in value) {\n value = value[part];\n } else {\n return \"\";\n }\n }\n \n return value || \"\";\n}\n\nfunction renderField(fieldName: string, fieldSchema: any, value: any, isEdit: boolean): any {\n const fieldType = getFieldType(fieldName, fieldSchema);\n const isRequired = fieldSchema?.required || false;\n const isReadonly = fieldSchema?.writeAccess === \"serverOnly\";\n \n const commonProps = {\n name: fieldName,\n id: fieldName,\n required: isRequired,\n readonly: isReadonly,\n class: `w-full px-3 py-2 border border-gray-300 rounded-md focus:outline-none focus:ring-2 focus:ring-blue-500 ${\n isReadonly ? \"bg-gray-100\" : \"\"\n }`\n };\n\n if (fieldType === \"checkbox\") {\n return (\n \n );\n }\n\n if (fieldType === \"number\") {\n return (\n \n );\n }\n\n if (fieldType === \"datetime-local\") {\n // Convert various date formats to datetime-local format\n let dateValue = \"\";\n if (value) {\n try {\n const date = new Date(value);\n if (!isNaN(date.getTime())) {\n dateValue = date.toISOString().slice(0, 16);\n }\n } catch (e) {\n // Invalid date, leave empty\n }\n }\n \n return (\n \n );\n }\n\n // For complex objects or long text, use textarea\n if (typeof value === \"object\" || (typeof value === \"string\" && value.length > 100)) {\n const displayValue = typeof value === \"object\" ? JSON.stringify(value, null, 2) : value;\n \n return (\n \n );\n }\n\n return (\n \n );\n}\n\nexport function DataForm({ type, schema, data }: DataFormProps) {\n const isEdit = Boolean(data);\n const fields = schema?.fields || {};\n \n // Get all field names from schema and existing data\n const allFields = new Set();\n \n // Add schema fields\n Object.keys(fields).forEach(field => allFields.add(field));\n \n // Add fields from existing data\n if (data?.data) {\n Object.keys(data.data).forEach(field => allFields.add(`data.${field}`));\n }\n \n const fieldList = Array.from(allFields).sort();\n \n return (\n

\n \n

\n {/* Metadata fields for editing */}\n {isEdit && (\n

Metadata (Read-only)

\n OID: {data.oid}\n

\n Created: {data.createdTime || \"N/A\"}\n

\n Last Updated: {data.lastUpdatedTime || \"N/A\"}\n

\n {data.UID && (\n

\n UID: {data.UID}\n

\n )}\n

\n )}\n\n {/* Data fields */}\n

\n {isEdit ? \"Edit\" : \"Create\"} {type} Data\n

\n \n {fieldList.length === 0 ? (\n

No schema defined for this type

\n You can still create data - fields will be auto-detected\n

\n \n Raw JSON Data\n \n \n

\n ) : (\n

\n {fieldList.map(fieldName => {\n const fieldSchema = fields[fieldName] || {};\n const value = getFieldValue(data, fieldName);\n \n return (\n

\n \n {fieldName}\n {fieldSchema.required && *}\n {fieldSchema.writeAccess === \"serverOnly\" && (\n (read-only)\n )}\n \n {renderField(fieldName, fieldSchema, value, isEdit)}\n {fieldSchema.format && (\n

\n Format: {fieldSchema.format}\n

\n )}\n

\n );\n })}\n

\n )}\n

\n\n {/* Actions */}\n

\n \n Cancel\n \n \n {isEdit ? \"Update\" : \"Create\"}\n \n

\n \n\n {/* Schema Information */}\n {schema && Object.keys(fields).length > 0 && (\n

\n View Schema Details\n

\n {JSON.stringify(schema, null, 2)}\n

\n )}\n

\n );\n}",[],[266,180,285],{"_104":292,"_97":211,"_163":293,"_165":272,"_166":145,"_167":168,"_169":118,"_106":294,"_101":33,"_171":189,"_173":295,"_174":22,"_175":-5,"_176":296,"_100":297},"c4cab440-1299-11f1-935e-42dde27851f2","019c96ee-0299-75ff-a0e4-f87af32ee320",["D",1772058706545],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface LayoutProps {\n title: string;\n children: any;\n}\n\nexport function Layout({ title, children }: LayoutProps) {\n return (\n \n \n \n \n {title}\n \n \n \n \n \n \n

\n {children}\n

\n \n \n \n );\n}",[],[266,180,211],{"_104":299,"_97":300,"_163":301,"_165":272,"_166":145,"_167":168,"_169":118,"_106":302,"_101":33,"_171":189,"_173":303,"_174":22,"_175":-5,"_176":304,"_100":305},"c4cad344-1299-11f1-935e-42dde27851f2","TypeSelector.tsx","019c96ee-0299-75ff-a0e4-fd88c285267d",["D",1772058706545],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface TypeSelectorProps {\n types: string[];\n selectedType?: string;\n search?: string;\n}\n\nexport function TypeSelector({ types, selectedType, search }: TypeSelectorProps) {\n return (\n

Select Data Type

\n \n

\n {types.map((type) => (\n \n

{type}

\n Click to view data\n

\n \n ))}\n

\n\n {types.length === 0 && (\n

No data types found

\n Make sure your Gigya DS credentials are configured correctly.\n

\n )}\n\n {selectedType && (\n

\n )}\n

\n );\n}",[],[266,180,300],[266,180],{"_104":308,"_97":220,"_163":116,"_165":267,"_166":145,"_167":168,"_169":118,"_106":309,"_101":33,"_171":223,"_173":310,"_174":22,"_175":-5,"_176":311,"_100":312},"c4cae32a-1299-11f1-935e-42dde27851f2",["D",1772058706545],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\nimport { Hono } from \"https://esm.sh/hono@4.0.0\";\nimport { readFile, serveFile } from \"https://esm.town/v/std/utils@85-main/index.ts\";\nimport { DSManager } from \"../shared/ds-manager.ts\";\nimport { DataForm } from \"./components/DataForm.tsx\";\nimport { DSViewer } from \"./components/DSViewer.tsx\";\nimport { Layout } from \"./components/Layout.tsx\";\nimport { TypeSelector } from \"./components/TypeSelector.tsx\";\n\nconst app = new Hono();\n\n// Unwrap Hono errors to see original error details\napp.onError((err, c) => {\n throw err;\n});\n\n// Initialize DS Manager\nconst dsManager = new DSManager();\n\n// Serve static files\napp.get(\"/frontend/*\", c => serveFile(c.req.path, import.meta.url));\napp.get(\"/shared/*\", c => serveFile(c.req.path, import.meta.url));\n\n// Main page - Type selector and data viewer\napp.get(\"/\", async (c) => {\n try {\n const selectedType = c.req.query(\"type\");\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n const search = c.req.query(\"search\") || \"\";\n\n // Get all available types\n const types = await dsManager.getTypes();\n\n let data = null;\n let schema = null;\n let totalCount = 0;\n\n if (selectedType) {\n // Get schema for the selected type\n schema = await dsManager.getSchema(selectedType);\n\n // Get data for the selected type\n const result = await dsManager.searchData(selectedType, search, page, limit);\n data = result.data;\n totalCount = result.totalCount;\n }\n\n return c.html(\n \n

DS Store Viewer

\n {selectedType && (\n \n Create New {selectedType}\n \n )}\n

\n\n \n\n {selectedType && data && (\n \n )}\n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Create data form\napp.get(\"/create\", async (c) => {\n try {\n const type = c.req.query(\"type\");\n if (!type) {\n return c.redirect(\"/\");\n }\n\n const schema = await dsManager.getSchema(type);\n\n return c.html(\n \n

\n ← Back\n

Create New {type}

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Edit data form\napp.get(\"/edit/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n\n const [schema, item] = await Promise.all([\n dsManager.getSchema(type),\n dsManager.getItem(type, id),\n ]);\n\n if (!item) {\n return c.html(\n \n

\n Item not found\n

\n ,\n );\n }\n\n return c.html(\n \n

\n ← Back\n

Edit {type}

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// API Routes\n\n// Get all types\napp.get(\"/api/types\", async (c) => {\n try {\n const types = await dsManager.getTypes();\n return c.json({ success: true, data: types });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get schema for a type\napp.get(\"/api/schema/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const schema = await dsManager.getSchema(type);\n return c.json({ success: true, data: schema });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Search data\napp.get(\"/api/data/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const search = c.req.query(\"search\") || \"\";\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n const result = await dsManager.searchData(type, search, page, limit);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get single item\napp.get(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n const item = await dsManager.getItem(type, id);\n\n if (!item) {\n return c.json({ success: false, error: \"Item not found\" }, 404);\n }\n\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Create item\napp.post(\"/api/data/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const body = await c.req.json();\n const item = await dsManager.createItem(type, body);\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update item\napp.put(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n const body = await c.req.json();\n const item = await dsManager.updateItem(type, id, body);\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Delete item\napp.delete(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n await dsManager.deleteItem(type, id);\n return c.json({ success: true });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Execute custom query\napp.post(\"/api/query\", async (c) => {\n try {\n const { query } = await c.req.json();\n const result = await dsManager.executeQuery(query);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Health check\napp.get(\"/api/health\", (c) => {\n return c.json({\n success: true,\n timestamp: new Date().toISOString(),\n service: \"Generic DS Store Viewer\",\n });\n});\n\nexport default app.fetch;",[],[266,220],[266],{"_104":315,"_97":316,"_163":317,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":318,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_176":319,"_100":328},"c4cb3d3e-1299-11f1-935e-42dde27851f2","shared","019c96ee-0299-75ff-a0e5-128278076c22",["D",1772058706545],[320],{"_104":321,"_97":322,"_163":323,"_165":317,"_166":145,"_167":168,"_169":118,"_106":324,"_101":33,"_171":189,"_173":325,"_174":22,"_175":-5,"_176":326,"_100":327},"c4cb0f4e-1299-11f1-935e-42dde27851f2","ds-manager.ts","019c96ee-0299-75ff-a0e5-0c58be42f7b8",["D",1772058706545],"// Generic Gigya DS Manager\n// Handles all interactions with Gigya Data Store APIs\n\nexport interface GigyaResponse {\n errorCode: number;\n errorMessage?: string;\n callId?: string;\n time?: string;\n statusCode?: number;\n statusReason?: string;\n}\n\nexport interface DSSearchResponse extends GigyaResponse {\n results?: Array<{\n oid: string;\n data: any;\n lastUpdated?: number;\n lastUpdatedTime?: string;\n created?: number;\n createdTime?: string;\n UID?: string;\n }>;\n objectsCount?: number;\n totalCount?: number;\n nextCursorId?: string;\n}\n\nexport interface DSGetResponse extends GigyaResponse {\n data?: any;\n oid?: string;\n UID?: string;\n lastUpdated?: number;\n lastUpdatedTime?: string;\n created?: number;\n createdTime?: string;\n}\n\nexport interface DSStoreResponse extends GigyaResponse {\n oid?: string;\n}\n\nexport interface DSSchemaResponse extends GigyaResponse {\n schema?: {\n fields?: Record;\n dynamicSchema?: boolean;\n };\n}\n\nexport interface DSTypesResponse extends GigyaResponse {\n types?: string[];\n}\n\nexport class DSManager {\n private domain: string;\n private apiKey: string;\n private appKey: string;\n private appSecret: string;\n\n constructor() {\n // Get credentials from environment variables\n this.domain = Deno.env.get(\"GIGYA_DOMAIN\") || \"accounts.eu1.gigya.com\";\n this.apiKey = Deno.env.get(\"GIGYA_API_KEY\") || \"\";\n this.appKey = Deno.env.get(\"GIGYA_APP_KEY\") || \"\";\n this.appSecret = Deno.env.get(\"GIGYA_APP_SECRET\") || \"\";\n\n if (!this.apiKey || !this.appKey || !this.appSecret) {\n console.warn(\"Missing Gigya environment variables. Some features may not work.\");\n }\n }\n\n private async makeRequest(endpoint: string, params: Record): Promise {\n const url = `https://${this.domain}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: this.apiKey,\n userKey: this.appKey,\n secret: this.appSecret,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`HTTP ${response.status}: ${text}`);\n }\n\n const result = await response.json();\n \n if (result.errorCode !== 0) {\n throw new Error(`Gigya API Error ${result.errorCode}: ${result.errorMessage || 'Unknown error'}`);\n }\n\n return result;\n }\n\n // Get all available data types\n async getTypes(): Promise {\n try {\n const response: DSTypesResponse = await this.makeRequest(\"ds.getTypes\", {});\n return response.types || [];\n } catch (error) {\n console.error(\"Error fetching types:\", error);\n return [];\n }\n }\n\n // Get schema for a specific type\n async getSchema(type: string): Promise {\n try {\n const response: DSSchemaResponse = await this.makeRequest(\"ds.getSchema\", {\n type,\n filter: \"full\"\n });\n return response.schema || null;\n } catch (error) {\n console.error(`Error fetching schema for type ${type}:`, error);\n return null;\n }\n }\n\n // Search data with pagination and filtering\n async searchData(\n type: string, \n searchTerm: string = \"\", \n page: number = 1, \n limit: number = 50\n ): Promise<{ data: any[], totalCount: number, objectsCount: number }> {\n try {\n let query = `SELECT * FROM ${type}`;\n \n // Add search conditions if provided\n if (searchTerm.trim()) {\n // Try to search in common text fields\n const searchConditions = [\n `data CONTAINS \"${searchTerm}\"`,\n `oid CONTAINS \"${searchTerm}\"`\n ];\n query += ` WHERE (${searchConditions.join(\" OR \")})`;\n }\n \n // Add pagination\n const start = (page - 1) * limit;\n query += ` LIMIT ${limit}`;\n if (start > 0) {\n query += ` START ${start}`;\n }\n\n const response: DSSearchResponse = await this.makeRequest(\"ds.search\", {\n query\n });\n\n return {\n data: response.results || [],\n totalCount: response.totalCount || 0,\n objectsCount: response.objectsCount || 0\n };\n } catch (error) {\n console.error(`Error searching data for type ${type}:`, error);\n return { data: [], totalCount: 0, objectsCount: 0 };\n }\n }\n\n // Get a single item by type and ID\n async getItem(type: string, oid: string): Promise {\n try {\n const response: DSGetResponse = await this.makeRequest(\"ds.get\", {\n type,\n oid,\n fields: \"*\"\n });\n\n if (response.data) {\n return {\n oid: response.oid,\n data: response.data,\n lastUpdated: response.lastUpdated,\n lastUpdatedTime: response.lastUpdatedTime,\n created: response.created,\n createdTime: response.createdTime,\n UID: response.UID\n };\n }\n \n return null;\n } catch (error) {\n console.error(`Error fetching item ${oid} of type ${type}:`, error);\n return null;\n }\n }\n\n // Create a new item\n async createItem(type: string, data: any): Promise {\n try {\n const response: DSStoreResponse = await this.makeRequest(\"ds.store\", {\n type,\n data: JSON.stringify(data),\n oid: \"auto\"\n });\n\n return {\n oid: response.oid,\n data\n };\n } catch (error) {\n console.error(`Error creating item of type ${type}:`, error);\n throw error;\n }\n }\n\n // Update an existing item\n async updateItem(type: string, oid: string, data: any): Promise {\n try {\n const response: DSStoreResponse = await this.makeRequest(\"ds.store\", {\n type,\n oid,\n data: JSON.stringify(data),\n updateBehavior: \"replace\"\n });\n\n return {\n oid,\n data\n };\n } catch (error) {\n console.error(`Error updating item ${oid} of type ${type}:`, error);\n throw error;\n }\n }\n\n // Delete an item\n async deleteItem(type: string, oid: string): Promise {\n try {\n await this.makeRequest(\"ds.delete\", {\n type,\n oid,\n fields: \"*\"\n });\n } catch (error) {\n console.error(`Error deleting item ${oid} of type ${type}:`, error);\n throw error;\n }\n }\n\n // Execute a custom query\n async executeQuery(query: string): Promise {\n try {\n const response: DSSearchResponse = await this.makeRequest(\"ds.search\", {\n query\n });\n\n return {\n results: response.results || [],\n totalCount: response.totalCount || 0,\n objectsCount: response.objectsCount || 0\n };\n } catch (error) {\n console.error(\"Error executing custom query:\", error);\n throw error;\n }\n }\n\n // Set schema for a type\n async setSchema(type: string, schema: any): Promise {\n try {\n await this.makeRequest(\"ds.setSchema\", {\n type,\n dataSchema: JSON.stringify(schema)\n });\n } catch (error) {\n console.error(`Error setting schema for type ${type}:`, error);\n throw error;\n }\n }\n\n // Delete schema fields\n async deleteSchemaFields(type: string, fields: string[]): Promise {\n try {\n await this.makeRequest(\"ds.deleteSchemaFields\", {\n type,\n dataSchema: JSON.stringify(fields)\n });\n } catch (error) {\n console.error(`Error deleting schema fields for type ${type}:`, error);\n throw error;\n }\n }\n}",[],[316,322],[316],{"_104":330,"_97":331,"_163":332,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":333,"_101":33,"_171":189,"_173":74,"_174":22,"_175":-5,"_176":334,"_100":335},"c4cf6580-1299-11f1-935e-42dde27851f2","main.tsx","019c96ee-0299-75ff-a0e5-420f45304b65",["D",1772058706545],[],[331],"files",[160,178,184,193,201,209,218,228,235,245,254,264,270,275,283,291,298,307,314,320,329],"counts",{"_340":33,"_341":168,"_342":33,"_343":344,"_348":349},"pulls","branches","forks","envVars",{"_345":346,"_347":33},"count",5,"emptyCount","connections",{"_345":33,"_350":33},"unfilledCount","contents",[353,356,359,362,365],{"_104":161,"_97":162,"_163":164,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":354,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_100":355},["D",1772058706545],[162],{"_104":229,"_97":230,"_163":231,"_165":-5,"_166":145,"_167":232,"_169":118,"_106":357,"_101":168,"_171":172,"_173":-5,"_174":22,"_175":-5,"_100":358},["D",1772058820543],[230],{"_104":265,"_97":266,"_163":267,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":360,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_100":361},["D",1772058706545],[266],{"_104":315,"_97":316,"_163":317,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":363,"_101":33,"_171":172,"_173":-5,"_174":22,"_175":-5,"_100":364},["D",1772058706545],[316],{"_104":330,"_97":331,"_163":332,"_165":-5,"_166":145,"_167":168,"_169":118,"_106":366,"_101":33,"_171":189,"_173":74,"_174":22,"_175":-5,"_100":367},["D",1772058706545],[331],"upstreamProject",{"_104":153,"_97":370,"_112":-5,"_113":-5,"_110":111,"_23":371},"os",{"_95":96,"_135":136},"upstreamBranch",{"_104":148,"_106":374,"_375":376,"_97":45,"_146":153,"_101":150,"_147":-5,"_149":-5,"_377":378,"_108":-5,"_157":22,"_110":111,"_156":96,"_16":122,"_155":370},["D",1749131789618],"updatedAt",["D",1762014309157],"lockfileKey","1764098888052-esm.town_v_dinavinter_os@169-main","emptyEnvVars","isNew","flags",[],"routes/_app.x.$handle.$name.environment-variables",{"_95":96,"_97":98,"_102":385,"_343":390,"_411":22},{"_104":105,"_97":98,"_106":386,"_108":-5,"_109":22,"_110":111,"_112":-5,"_113":-5,"_14":114,"_115":116,"_117":118,"_119":-5,"_120":-5,"_121":33,"_16":122,"_123":-5,"_124":-5,"_125":126,"_127":126,"_128":129,"_130":129,"_131":129,"_132":126,"_133":126,"_23":387,"_137":388,"_142":389,"_157":22},["D",1772058706545],{"_95":96,"_135":136},{"_95":96,"_139":136,"_14":114,"_140":141},{"_101":144,"_97":45,"_104":145,"_146":105,"_147":148,"_149":150,"_151":111,"_152":153,"_154":122,"_155":98,"_156":96},[391,396,400,404,408],{"_392":393,"_106":394,"_375":-5,"_112":74,"_395":22},"key","GIGYA_APP_ID",["D",1772060146271],"isEmpty",{"_392":397,"_106":398,"_375":399,"_112":74,"_395":22},"CONFIRM_CLEANUP",["D",1772058706545],["D",1772058896406],{"_392":401,"_106":402,"_375":403,"_112":74,"_395":22},"GIGYA_API_KEY",["D",1772058706545],["D",1772060036562],{"_392":405,"_106":406,"_375":407,"_112":74,"_395":22},"GIGYA_APP_SECRET",["D",1772058706545],["D",1772060130518],{"_392":409,"_106":410,"_375":-5,"_112":-5,"_395":22},"GIGYA_DOMAIN",["D",1772058706545],"isTeamOrg","actionData","errors"]

Key	Description
GIGYA_APP_ID
CONFIRM_CLEANUP
GIGYA_API_KEY
GIGYA_APP_SECRET
GIGYA_DOMAIN

dinavinter

gigya

Environment variables