@magnificent-energy-493, we are trying to confirm that we are following registration webhook steps correctly. Based on the documentation, if we send the following body to the registration endpoint via the method in the SDK:

{
  "csrf_token": "VALID_CSRF_TOKEN",
  "traits.preferred_name": "Terry Testington",
  "traits.email": "<mailto:terry@testing.com|terry@testing.com>",
  "traits.phone": "VALID_MOBILE_NUMBER",
  "method": "password",
  "password": "S0m3F@ncyP@55w0rd",
  "transient_payload.terms_accepted": true,
  "transient_payload.marketing_opt_in": false,
  "transient_payload.identity_type": "customer",
  "transient_payload.identity_issuer": "ory"
}

^ Does this look correct? Also, what steps need to be taken from the web hooks side once this request is correct and sent through, in order to ensure that the

transient_payload

sent above ends up in the metadata_public for the user's identity? Tagging my colleagues @calm-agent-17042 and @important-area-42405 for reference

@magnificent-energy-493 A follow on question with regards to updating identity metadata on registration. When I set

parse: true

my id becomes

Identity id: 00000000-0000-0000-0000-000000000000

. How do I update my identity metadata without causing this to happy?

Tagging @fast-lunch-54279 as this is critical and blocker

@high-optician-2097 and @proud-plumber-24205 have also helped me in the past

If you need the identity id and you need to modify the identity on creation, you need another (potentially second) webhook with parse set to false. the identity id is only created when it’s saved to the database. Also please be respectful with pings - there were 4 people pinged including emails sent for a question asked a few hours ago. We won’t be able to process your requests if you engage everyone and you’ll get different answers from different people!

@high-optician-2097 Thanks for the help . This issue been resolved. Apologies for following up this issues on multiple threads. We will use slack going forward.

Thank you, appreciate it!