Organization contacts: org id in URL path

While exercising organization_contacts we found that passing people.me().orgId as returned (the long base64-style opaque id) into paths such as contacts/organizations/{orgId}/contacts/search can produce HTTP 403 (“access is not allowed”), even when other APIs work with that same value.

Decoding the opaque id (base64 → UTF-8) yields a ciscospark://…/ORGANIZATION/{uuid} URI. Using the UUID segment (e.g. cea68dcc-7b72-4d9c-891d-25fbc6cfa30b) as {orgId} in the organization-contacts path succeeds

Can you please update the implementation to decode at least during testing? If only tests are updated, please document this detail.

Let me know if you have any questions. I look forward to hearing from you.