utilRegisteredCorporation
Prev: utilRegisteredCharacter
As stated in utilRegisteredKey above this table becomes optional when registered_mode = optional and for the corporation associated with a key you can farther restrict the column values from it or the utilSections table. Note that each of the null-able columns is independent of the others. For example the activeAPIMask column for a row in utilRegisteredCorporation can have a different value but for the same row proxy can still be null and the value from the other two tables would be used instead.
Note that only 'Corporation' type keys are used for this table. This doesn't mean that Yapeal can't end up trying to get the same API multiple times, once for each registered key since more than one character can have a corporation key even ones from characters on different accounts. A single character on the same account can also have more than one corporation key. This shouldn't actually result in the APIs being retrieved multiple times since the ownerID column = corporationID in the utilCachedUntil table and any APIs that have already been updated by another key will be ignore by the current one because the time to retrieve it hasn't come up yet. Like with the utilRegisteredCharacter table you could try filtering them in the application but it probably isn't worth the effort needed to do so.
Next: util Tables Summary