Where does the API namespace value come from?

[mcconnellsj]

Hi

We have just started creating a scripted REST service for an integration.

We are creating the service in the Global application.

On the initial form, the "API namespace" is automatically populated and greyed out.  The value in there is something like "abcuk", that is, it isn't a number - which I have seen in the examples and tutorials.

The actual value there looks similar to the previous name of our company, and, we would like it to reflect the new name.

Is it possible to rename the API namespace?

How did it come to have this name in the first place?

Thanks in advance.

[Deepak Ingale1]

If you want to make any changes, please raise request with HI since this is unique prefix per customer and specially created for scoping around configurations across customers. SN HI support team will be able to help you on that and if required, then can make changes across instance stacks what your company have.

[bernyalvarado]

Agree with Deepak's comments.

[bernyalvarado · Accepted solution]

They (Hi support) should also be able to tell you if there's any implications of making this change. Just make sure to clearly outline that when you make the request.

All the best sir!

[mcconnellsj]

Hi

HI confirm that the namespace cannot be changed, even if the name of your instance changes.

Unluckily for us, we are now stuck with an embarrassing namespace that is the previous name of the company - not very professional.

There doesn't seem to be anyway of changing this with respect to the namespace in an API address.

Thanks for your help anyway

S.

[bernyalvarado]

That's a bummer! I'm sorry to hear that.

Is that the only instance that you guys have for developing "scoped applications"? Do you have an instance with your new company name? Or perhaps ServiceNow can grant you a new instance with the new company name and you can rewrite your scripted rest service in the new instance. 

Thanks,

Berny