Using my own job id

Hello,

After I send the job, I have job id, which looks like this.
<JobId>
<XDN>test2</XDN>
<MRN>1498517</MRN>
</JobId>

Is it possible to use our own job id? Can I set job id while sending job? for example, when I send job, in job request i setup my own job id
MWARE-123456
and later when I request status of the job, I will use my own job id instead of XDN and MRN.

Thanks,

Alexander.

Find more posts tagged with

Comments

skamens

You can not specify the Job ID - that is assigned by the system.

You can specify a MessageId with your input, which uniquely identifies the job. If a second request comes in with the same MessageId, a new job will not be created, but rather the old JobId will be returned. This is done so that you can avoid getting duplicate jobs as a result of possible duplicate submissions due to network issues and such.

However, note that the MessageId needs to be unique across our entire system (not just your jobs). So if you do decide to use it, we recommend that you prefix your MessageId with your user ID, and make sure they are unique among your own jobs.

When you want to query for a job, you must use the JobId that is provided to you by the system, so the best thing to do is to store the Job ID that you receive so you can use it to query for status.

mbe1

Couple of questions on this:

1) How long are message id's stored for? ( how many days?)

2) If one user id sends a fax using a messageid that has been used before by another userid, will that user get the job number of the other users job instead of the fax being sent?

3) Do you recommend not filling the message Id field so there is no possibility of duplication or error bwteen various users? If empty should it be not filled or be a blank charecter?

skamens

To answer your questions:

Message ID's are stored in the system for a long as their associated jobs are stored. That varies from job to job and from account to account, but is at least a few days. Most users that *do* use a MessageID will include a date and time as part of the value (along with their user ID) to help ensure uniqueness.
Yes, if one user happens to use a MessageID that is associated with a job that belongs to another user, the system will return that other job. However, the first user would not have permissions to actually retrieve and look at that other job, since it belongs to someone else.
This really depends on your application. If you are confident that you can maintain uniqueness of your jobs without using a MessageID, then you should just leave that element out. But if your application is sensitive to the possibility of duplicate jobs/deliveries, then you should create a MessageID that will help to ensure that uniqueness. I can tell you that with the exception of people using a very simplistic MessageID (like "test message" or something), users generally have no problem coming up with a MessageID that doesn't clash with what other people are using.

skamens

Addendum - for #2 above, I'm told that the API will not return the job ID if it does belong to the requesting user.