![]() type: Can be "ItemExchange", "Auction", "Loan" or "Courier".acceptorID: The character who has accepted the contract, 0 if none.assigneeID: The character or corporation who was assigned to the contract, 0 if none.issuerCorpID: The corporation of which the issuer was a member of when the contract was issued.issuerID: The character who issued the contract.Each item in the list has the following attributes: ![]() A single contract can be retreived using the contractID parameter. char/: Lists contracts issued within the last month as well as all contracts marked as outstanding or in-progress. Well, three pairs of pages since you can fetch character and corporation contracts. We created three new pages to display contract information. To make a long story short, we decided to stick with that strategy. I posted a dev blog a while ago which explains the strategy we were going with at the time. Here's another popular request from the API community. You can find some examples of how to use the keys in the API and how to create the template/predefined links there. Technical information in CCP Stillman's dev blog from the testing period of the new keys still stands. You can find the keyID in the first column (called ID) on the API key management website, vCode stands for Verification Code and is displayed in the same table for each key. To use the new keys in the API you can throw out the old userID and apiKey URL parameters and use keyID and vCode instead. We'll keep an eye on the key usage though and let you know well before we flip the switch. We don't have an exact date for cutting them off we want to give developers plenty of time to make the switch and make users aware of the changes, but we are measuring this in weeks and considering something in the order of 4-8 weeks. The old one will, however, remain open and you can still create and use the old keys in the API for a while. The management web for API keys has been moved to the EVE Support website. If you have a character that's a CEO or a corporate director then you can create a corporation key which unlocks the character's corporation information.īy templates, we mean that third-party developers can provide users with links to the API key creation form with a pre-defined access mask which describes what is needed for their application to work properly and the required API pages will be selected automatically on the form. If you select one of your characters then the key will only apply to the selected one, if you don't the key will provide access to all your characters' info. You can also customize the key's access to API information based on characters. When you quit your corporation you can cut off any access to your API information your former boss may have had without having to create a new key for your third-party apps. Say you want to give the director of your corporation access to your wallet info but only for today, you can create a key that only unlocks that information and expires tomorrow. The concept of customizing your API keys is all about being able to control what information can be accessed in the API with a particular API key, and for how long. Access to character- and corporation information separated.Customizable access to the API + Templates. ![]() The new API key system offers a variety of new features that we hope will fill both third-party developers' and third-party application users' hearts with light, joy and furry little animals. You've been asking for this one for a while now and here it is. Most of you API-savvy programmers probably know how the new toys work to every last detail, but I'm still going to spell them out just to make sure everything is clear. ![]() For a while now we've had the latest API updates running on a SISI setup on as well as the new key management web on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |